cloud-security-xsuaa-integration | Integration libraries and samples for authenticating users and clients bound to XSUAA authentication | OAuth library
kandi X-RAY | cloud-security-xsuaa-integration Summary
kandi X-RAY | cloud-security-xsuaa-integration Summary
Authentication services provided by the xsuaa service on SAP Cloud Platform or SAP HANA XS Advanced rely on usage of the OAuth 2.0 protocol and OAuth 2.0 access tokens.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Extracts the broker token .
- Request an access token .
- Returns true if token is in foreign mode .
- Parse the private key from the given private key .
- Retrieve token keys .
- Request user token .
- Gets the audience from a token .
- Creates JSON web key from given JSON object .
- Creates the default validators .
- Loads all service configurations for the given service .
cloud-security-xsuaa-integration Key Features
cloud-security-xsuaa-integration Examples and Code Snippets
Community Discussions
Trending Discussions on cloud-security-xsuaa-integration
QUESTION
We're trying to use SAP SpringBoot Starter XSUAA 2.7.8 (https://github.com/SAP/cloud-security-xsuaa-integration) together with the SAP CloudSDK for Java 3.32.0.
The CloudSDK depends on part of the xsuaa (java-api, java-security, tokenclient, java-security-test) version 2.7.8, but does not use spring-xsuaa. The CloudSDK also depends on Spring Security 5.4.1. When we add xsuaa-spring-boot-starter, our security integration tests break, and at runtime we run into token validation errors at the "rest api" side (rest controllers) of our app. It seems to be due to the fact that xsuaa-spring-boot-starter depends on Spring Security 5.3.4.RELEASE.
We get errors saying: java.lang.NoSuchMethodError: 'java.util.Map com.nimbusds.jose.Header.toJSONObject(). This is a know issue with spring security 5.4.1 (https://github.com/spring-projects/spring-security/issues/9120). As the issue states spring security is meant to be used with springboot 2.4 and not 2.3 which is used by the cloud sdk.
We've not been able to resolve this issue. Can this be the cause of different dependencies? If so, any ideas on how to resolve these?
Thanks,
Danny
...ANSWER
Answered 2020-Nov-24 at 08:18Edit: As of version 3.33.0
the SDK comes with the below configuration by default in the Spring Archetype.
Your observation is correct, this is a dependency conflict introduced by the different Spring security versions.
In case you are using the SDK BOM you need to explicitly set the Spring security version before it would be set by the SDK BOM:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cloud-security-xsuaa-integration
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page