
NamingStrategy
interface has been redesigned entirely, leading to compilation errors if the existing implementation is used.DefaultNamingStrategy
has been renamed to S4HanaNamingStrategy
. We kept the latter as the default strategy to ensure better compatibility.DefaultNamingStrategy.NameSource
enumeration has been moved to the package rather than being nested inside of a class.ScpCfDestinationLoader
always performs an initial lookup request against the destination service to get the authentication type configured in the destination. This guarantees that we perform a user token exchange if it's required to authenticate at the target system. On the flip side, this request will be redundant if we know beforehand the token exchange is required. Having to load such a destination often might lead to a significant performance toll.ScpCfDestinationTokenExchangeStrategy
we're now able to skip the initial authentication type lookup request when loading a destination on BTP Cloud Foundry and do only the token exchange to boost performance. From the options below you can see that having just an authentication type lookup is also possible.LOOKUP_THEN_EXCHANGE
(default)LOOKUP_ONLY
EXCHANGE_ONLY
DestinationOptions options =
DestinationOptions
.builder()
.augmentBuilder(
ScpCfDestinationOptionsAugmenter
.augmenter()
.tokenExchangeStrategy(ScpCfDestinationTokenExchangeStrategy.EXCHANGE_ONLY))
.build();
Try<Destination> destination = DestinationAccessor.getLoader().tryGetDestination("MyDestination", options);
Principal#getAuthorizationsByAudience
provides OAuth authorization scope of the principal grouped by the audience.[ "a.Display", "b.Change.Things", "c.Ignore" ]
{aud: [a, b]}
Principal#getAuthorization
API on an App legible only for the audience "a", you'll get just [Display]
scope.{a: [Display], b: [Change.Things]}
pom.xml
file. Bump the version of com.sap.cloud.sdk
dependency to 3.48.0
similar to the XML code snippet below and you're done! Mind, because Maven Central relying on CDN it takes a bit of time for the new maven module to be distributed.<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.sap.cloud.sdk</groupId>
<artifactId>sdk-bom</artifactId>
<version>3.48.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
<!-- possibly further managed dependencies ... -->
</dependencyManagement>
mvn clean install
from the command line in the root directory of your project.npm update
in the root folder of your module. Note that this will also update other modules unless you explicitly specify which packages to update. If you want to check beforehand what will change, use npm outdated
.You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
14 | |
12 | |
12 | |
9 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 |