Hi Samuli,
I was able to setup the IDP and SAML for SSO. However, I ran into few issues. I was hoping if you would have any insights or suggestions.
Web Version #
HTTP is working via OKTA (SAML-Identity Provider) SSO as expected.
HTTPS fails on the first attempt and prompts me for a user name/password, but if I refresh the same web browser, HTTPS also works on the second attempt.
Any suggestions how to get past this issue?
Desktop client Version#
Whenver I access web dynpro app via the client version, I get a security warning from the NWBC client, as my SAP server and Identity provider are on two different domains. I know reading through the blogs and as per note # 1378659 & http://help.sap.com/saphelp_nw73ehp1/helpdata/en/c5/18826ad1e944dfb39aa1d0fe3a188a/content.htm?frameset=/en/66/48a793bc2f4ec5bdb8e7e93ea6cd9f/frameset.htm
there is a way to bypass this security warning in the older versions of NWBC client. However, we are at the latest version NWBC 4.0 and the solution to bypass the security warning doesn't work. I did open an OSS message with SAP for this issue and they are suggesting this to be a consulting issue. The URL that I am calling from the NWBC client is the my Identity provider's SSO URL.
In case I use SAP's nwbc sicf HTTP URL from the nwbc desktop client instead of the IDP's SSO URL, it looks like the authentication takes place via the SAML assertions, but the client pop-up just hangs with a blank screen.
Any suggestions on this issue? Thanks in advnace.
Thanks
Dhee