cancel
Showing results for 
Search instead for 
Did you mean: 

S4HC Live connection SAPEMC in Analytics Cloud (SAC): Unable to authenticate

MKreitlein
Active Contributor
0 Kudos

Dear Community,

I'm trying to setup the SAC Live connection to S4HC, called "SAPEMC" for specific Business Content to be activated.

Unfortunately it does not work, and I've got no idea why.

I went through all related information, attachments in https://me.sap.com/notes/3013006

As well as the SAP Help pages: https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/0485d540e0b340a0bc0da... ... but the error or solution is not described anywhere.

See my issue:

I think, I set up the communication system, arrangement and user correctly, since my login credentials (of my Inbound user) are working fine, when I open the URL to my S4HC server: https://myNUMBER-api.s4hana.cloud.sap/sap/bw/ina/GetServerInfo

The answer is:

I tried it with or without "-api"... the error message is the same.

Can anybody, who sucessfully implemented already some S4HC related content in SAC, let me know if you had the same issue or which guide you followed ... or anybody else with some knowledge... what could I check more?

The Chrome Debugger Tool just states:

But what is the root cause?

Thanks, Martin

JulianoRomanato
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello m.kreitlein.

How are you? I have excluded the Tag "SAP S/4HANA Cloud" and included the Tag "SAP S/4HANA Cloud Extensibility" for this question, as Integrations are related to Extensibility.

Regards.

Juliano Romanato.

Accepted Solutions (0)

Answers (1)

Answers (1)

Tayane
Advisor
Advisor
0 Kudos
MKreitlein
Active Contributor
0 Kudos

Hello Tayane,

thanks a lot for your feedback... so regarding the notes, you mean to say, that the Inbound User, created in S4HC also needs to be provisioned in the Identity Provider?

But when trying to setup the connection, there are explicitly two fields for user and password, see above.

And for my user... the SAML Identity Provider for SAC is the same, which we use for the S4HC. In both SSO works fine.

So, this does not really explain my problem?!

Regards, Martin