1- [ ![ Release] ( https://jitpack.io/v/hmcts/idam-legacy-auth-support.svg )] ( https://jitpack.io/#hmcts/idam-legacy-auth-support )
2- [ ![ JitPack Badge] ( https://github.com/hmcts/idam-legacy-auth-support/actions/workflows/jitpack_build.yml/badge.svg )] ( https://github.com/hmcts/idam-legacy-auth-support/actions/workflows/jitpack_build.yml )
1+ [ ![ Azure Build Badge] ( https://github.com/hmcts/idam-legacy-auth-support/actions/workflows/ado_artifacts_build.yml/badge.svg )] ( https://github.com/hmcts/idam-legacy-auth-support/actions/workflows/ado_artifacts_build.yml )
32
43# IdAM Legacy Auth Support
54A Java module to simplify IdAM password grant calls, and S2S lease calls.
@@ -24,7 +23,7 @@ Once you have integrated with spring security you can user the standard annotati
2423
2524Note that the SIDAM team do not maintain S2S, but have included support for it here for simplicity.
2625
27- The library has auto configuration enabled based on spring properties, so all you need to do to start using it is import the library into
26+ The library has auto configuration enabled based on spring properties, so all you need to do to start using it is import the library into
2827your spring boot project and apply the correct configuration as described below.
2928
3029### Spring Password Grants
@@ -59,7 +58,7 @@ spring:
5958 - roles
6059```
6160
62- Once that is done then any feign calls that you make that match the ` endpoint-regex ` will have an Authentication header with the
61+ Once that is done then any feign calls that you make that match the ` endpoint-regex ` will have an Authentication header with the
6362password grant bearer token. The fetching/caching of the token is handled by spring security.
6463
6564When the password grant support is active you will see a message similar to the following on application startup:
9695 testing-support:
9796 enabled: true
9897```
99- This can be useful if you are developing before your microservice has been deployed to S2S. When running in testing-support mode
98+ This can be useful if you are developing before your microservice has been deployed to S2S. When running in testing-support mode
10099you will see a message similar to the following at startup:
101100```
102101RpeS2SAutoConfiguration idam-legacy-auth-support: Configured s2sTestingSupportAuthTokenGenerator for service: my-service-s2s-id
0 commit comments