Skip to Content

SSO Setup for SAP Analytics Cloud using okta as an Identity Provider

This blog post is intended to help customers using okta as an IDP to configure SAML SSO between SAP Analytics Cloud and SAP HANA.

The setup of SSO between Sap Analytics Cloud(SAC) and HANA is divided into 3 parts :

  1. Setup of SSO between the IDP and SAC using SAML
  2. Setup of SSO between the IDP and HANA
  3. Creating a HANA direct connection from SAC

 

Part 1. Setup of SSO between the IDP and SAC.

a. Login to the SAC application as an administrator and navigate to System -> Administration -> Security.

b. Click on Edit connection and choose SAML Single Sign-On

c. Download the service provider metadata.

This process would download a metadata file similar to this –

<ns3:EntityDescriptor

xmlns:ns2=”http://www.w3.org/2001/04/xmlenc#”

xmlns=”http://www.w3.org/2000/09/xmldsig#”

xmlns:ns4=”urn:oasis:names:tc:SAML:2.0:assertion”

xmlns:ns3=”urn:oasis:names:tc:SAML:2.0:metadata” ID=”S9653fde0-4faa-4ab4-bf3b-08cf21cb7715″ entityID=”XXXX.XXXX.XXXX”>

<ns3:SPSSODescriptor AuthnRequestsSigned=”true” protocolSupportEnumeration=”urn:oasis:names:tc:SAML:2.0:protocol”>

<ns3:KeyDescriptor use=”signing”>

<KeyInfo>

<KeyName>XXXX.XXXX.XXXX</KeyName>

<X509Data>

<X509Certificate>MIIC9DCCAdygAwIBAgIIQUUHCtq7+SwwDQYJKoZIhvcNAQELBQAwOjE4MDYGA1UEAxMvaHR0cHM6Ly9hY2NvdW50LnVzMS5oYW5hLm9uZGVtYW5kLmNvbS9iZThhMTM2YWYwHhcNMTYxMDIwMDA0ODE1WhcNMTcxMDIwMDA0ODE1WjA6MTgwNgYDVQQDEy9odHRwczovL2FjY291bnQudXMxLmhhbmEub25kZW1hbmQuY29tL2JlOGExMzZhZjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJj8+qGY4Y3ONYUpYOwMWyAG7t80DQnLh92ynfMtj8gZAvTijEdgZ896THWZxNg3P+xxxx.xxxx.xxxx+PECAwEAATANBgkqhkiG9w0BAQsFAAOCAQEALcIqrJ40yhqswKXsCnORSuQqmhwj7PKM0DBxSRq9JWMl31iEjsPc2J7Ywz4opgILQYiFgSb2HON0iyKD1QyZJaA9OR0apjOcc/XXX.XXPeO0OA/Db4vv+PV4EM3C0D+yFwnlKvTIT39jH2yxHGWKiQKcow==</X509Certificate>

</X509Data>

</KeyInfo>

</ns3:KeyDescriptor>

<ns3:SingleLogoutService Binding=”urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST” Location=”https://xxxx.xxxx.xxxx”/>

<ns3:SingleLogoutService Binding=”urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect” Location=”https:// xxxx.xxxx.xxxx “/>

<ns3:AssertionConsumerService index=”0″ isDefault=”true” Binding=”urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST” Location=”https:// xxxx.xxxx.xxxx “/>

</ns3:SPSSODescriptor>

</ns3:EntityDescriptor>

d. In your okta system, add a new application and enter the values as requested by the okta application.

Ensure that you fill the values based on the metadata.xml output from the SAC application.

e. Create a .der file eg. SAC.der and create a certificate like this –

—–BEGIN CERTIFICATE—–

<Include your certificate from the metadata file that was generated>

—–END CERTIFICATE—–

f. Upload the certificate in the SAML settings of the okta application

g. Click on Next and Finish to create an application in okta.

h. Map the application to either send email-id, user-id or Custom SAML user Mapping. Your okta administrator should be able to take care of this part.

i. You should now be able to download a Metadata file from okta.

j.Upload this metadata file into your SAC application under the SAML SSO configuration.

k. Choose a user attribute to map to your identity provider.

l. Verify your account with the identity provider.

m. Once the account is verified Save the settings.

n. You should now be able to do a SSO to SAC based on your okta credentials.

 

Part 2. Setup of SSO between the IDP and HANA.

a. Refer to the documentation available here to set up SAML SSO between IDP and HANA https://help.sap.com/http.svc/rc/00f68c2e08b941f081002fd3691d86a7/release/en-US/780842e11ee44dd6b5e7bd23cf393aff.html

Follow the above documentation for the pre-requisites until Step 4. Verify end-users’ web browser configuration and access.

 

Part 3. Creating a HANA direct connection using SAML.

a. Create a new Connection in SAC

 

b. Add new live data connection of type SAP HANA

c. Fill the required fields in the HANA connection as seen below-

 

d. Click on OK.

 

You have now configured SSO between your SAC and HANA using Okta IDP.

You can go ahead and create models based on the newly created HANA connection as well as create stories and DiBO with this connection.

 

Additional helpful articles-

1. SAML authentication in SAP Analytics Cloud

https://blogs.sap.com/2017/07/13/saml-authentication-in-sap-analytics-cloud/

2. Multiple IDP’s for HANA XS Artifact – BusinessObjects Enterprise Platform Perspective

https://blogs.sap.com/2017/06/05/multiple-idps-for-hana-xs-artifact-businessobjects-enterprise-platform-perspective/

3. KBA 2487116 for AD FS configuration and KBA 2487567 with steps on troubleshooting SAML.

7 Comments
You must be Logged on to comment or reply to a post.
  • Hi Jagdeesh,

    I have done SAML configuration for SAP HANA 2.0 But i am getting 403 forbidden error Can you please help which URL should i mention in single sign on URL field and audience URI field in okta and to which package in XS administration should i enable the SAML authentication.

    /
  • Few notes for mapping AD groups to Team/ Roles, when OKTA as IDP, is used.

    1. We need to have Groups=sac as static User attribute, not under Group Attribute Statement
    2. The attributes ‘custom1’, ‘custom2’ etc. needs to be under Group Attribute Statement, with the AD groups comparison.
  • Thank you for the nice article! It helped me a lot!

    I have few things to add:

    1. First of all it was a bit difficult to understand in what tag of the SAC XML file is the information needed in the specific Okta field. In the beginning we mixed up some of the fields.
    2. I don't know how was it when this article was written, but now Okta has Classic View and Developer console and you can only create apps like this in the Classic view
    3. I needed to set up SSO with SAP BW and I used the tutorials provided in SAC. I configured SAML 2.0 Local and trusted providers but the SAML 2.0 activation changed the SOAP default way of communication and our POS server stopped communicating with the BW PIPE. To fix the problem I changed the SOAP service setting to use SAML 1.1. Otherwise, BW always connects to Okta and pops up an error, because the sales server's user in not in the Okta users list and the machine isn't added as an app there.
  • Hi Jagdeesh

    Just a little clarification on SSO.  It sounds like the users have to be manually created/uploaded to SAC beside being created in Okta.  My previous experience with BOBJ, you didn't have to do that once the user was defined in Active Directory and SSO was setup.  New users got imported into BOBJ whenever there were new users were added in AD (thru BOBJ background process).   Could you please clarify that for me?  Is there a way to automate this process (without manually creating users in SAC) once the SSO is setup?

     

    Thanks

    Abdul