Hello guys,
I'm trying to install the ABAP SDK on-premise edition on a SAP-ECC server. I have done all the steps and in the end trying to check the authorization configuration I have this error:
I didn't find this error in the Troubleshooting guide. Someone can help me?
Thanks
Michele
Hello @Michele_Q ....Thanks for writing to us. Please refer to the link to the section here in our troubleshooting document to resolve this issue. Let us know how it goes.
Hello @devesh-sapcloud ,
I did not find anything useful in the troubleshooting document. Anyway, I have another question: the sample RFC connections created after importing the transport requests of the ABAP SDK should work if the SAP server can ping the endpoint? Because the RFC test connection fails but the server can ping those endpoints. Does the RFCs also require open inboud connection?
Thanks,
Michele
Hi @Michele_Q - Please follow https://medium.com/google-cloud/setting-up-jwt-based-authentication-in-abap-sdk-for-google-cloud-e42... for a step by step guide with screenshots on how to setup JWT based authentication. There are 2 service accounts - one for JWT signing and one for API call. Make sure the steps are completed appropriately for both service accounts.
As for the RFC destinations, ABAP SDK only needs to make outbound calls to these endpoints. There is no need for opening up inbound connection. If connection test fails, please check network & firewall logs where it is failing.
Regards,
Ajith
Hello @ajith-sap , I should have solved the issue but I don't understand: basically in order to solve I had to switch the service account used in the "Configure Client Key" tcode. Initially I used, as indicated in the documentation, the service account created with the APIs authorizations (
Thanks
Michele
Hi @ajith-sap , I did solve by switching the gcp service account used in the sap customizing: in the client key table tcode in SPRO I added the service account created in the gcp with the APIs authorization (as stated in the documentation) but only when I used the service account for the token creation that connection to the GCP started to work!
Thanks
Michele