Hi all,
I have developed an extension (java) application for Success Factors and it works fine on localhost with the basic authentication based destination. When I deployed my application to the cloud platform, it worked fine with the same type of destination. However when I tried to change it to the OAuth2SAMLBearerAssertion type (using the instructions at the related document), it didn't work. No reaction. And using trace, I got these which might be considered as a clue;
#com.sap.core.connectivity.httpdestination.impl.headerproviders.AbstractAssertionHeaderProvider#
Cannot generate OAuth 2.0 SAML Bearer Assertion because there is no user logged in the current thread.
org.apache.http.wire
Configuration with the respective path and name was not found.
At the same account using the web ide, I created an application with the help of templates connected to the same SF instance, same company, same service. Then I configured OAuth2SAMLBearerAssertion like I did for the previous one. With this approach I was forwarded to the SF system for authentication, got authenticated by the SF system, application started but retrieved no data. The message is ;
The requested resource was not found (Inside the UI5 App)
and at the browser console
Failed to load resource: the server responded with a status of 500 (Internal Server Error) https://sfodata-<HCPACCOUNT>.dispatcher.us1.hana.ondemand.com/destinations/<Dest_Name>/$metadata
Where do I need to check or is there any other necessary steps that I'm missing ? I'm using a trial account.
- Activated extension management
- Configured roles/permissions
- Deployed app
- Registered ext. app as AACS
- Registered OAuth client for odata access
- Configured dest. (OAuth2SAMLBearerAssertion )
Cheers.