2 weeks ago
Hello the community,
First time here and I'm asking to myself if someone has the same case than me.
I did all the configuration for SAP DRC relevant for our SAP ECC6 EHP8 (SP24) system.
The connection from Cloud Connector to the backend is OK and the ressource is available. The connection from BTP to the backend through the dedicated destination is OK when I test it. My issue is located on the created RFC type G I had to create with the oAuth2 configuration. I did all the chapter "Managing RFC Connections for SAP Document and Reporting Compliance, Cloud Edition" of the documentation : https://help.sap.com/docs/cloud-edition/sap-document-and-reporting-compliance-cloud-edition/managing...
I first met two scenarios.
So I checked note https://me.sap.com/notes/0003412080/E without success.
I really don't know where I failed. In SE80, all is done for the dedicated package.
In OA2C_CONFIG, I mentioned the clientID, clientSecret and the related URLs.
Authorization Endpoint : <enterprise>-drc-cloud-dev.authentication.eu02.hana.ondemand.com/oauth/authorization
Token Endpoint : <enterprise>-drc-cloud-dev.authentication.eu02.hana.ondemand.com/oauth/token
And the RFC configuration as been done as described...
Type : G
Host : drcc-test.c-257d320.kyma.ondemand.com
Path Prefix : /
Port : 443
Logon with User : Do not use a user
=> OAuth Settings => OA2C profile selected
Security Options, SSL Active
=> SSL Certificate ANONYM SSL Client, in which the ISRG Root X1 certificate has been set.
All the relevant oAuth2 SICF services seem to be activated.
The report OA2C_GENERIC_ACCESS return seems to be OK.
I'm still checking with SAP through a dedicated case but I don't know if I'm well understanded.
Thank you for your time and thank you if someone can help.
Have a nice day.
Regards.
Axel .
Request clarification before answering.
Hello everyone,
SAP finally answered to my case with the following : "I have verified the configuration of [your dedicated] RFC Destination and it is giving me the 404 error. Which signified that the connection is working fine. Refer screenshot."
So, even if in my case I used the oAuth2 authentication method instead of the certificate one, and even if the official documentation says that I should have the return code 401, the 404 seems to be also OK.
Kind Regards.
Axel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 8 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.