-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use new token api service #1156
Conversation
fd9fbfc
to
6756283
Compare
b4d883c
to
f2c28f8
Compare
7bce5c2
to
9f22369
Compare
9f22369
to
4c1856d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
migration note is missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
xxx
src/app/extensions/punchout/identity-provider/punchout-identity-provider.spec.ts
Show resolved
Hide resolved
92e8785
to
748942f
Compare
e29dc52
to
68ab8b8
Compare
Azure Demo Servers are available: |
68ab8b8
to
d261acd
Compare
b591544
to
a9195ad
Compare
* old token behavior with the token exchange for each request is replaced by the exchange via token API * get tokens for an anonymous user and for a user with credentials * refresh token before it is expired * revoke token on logout BREAKING CHANGES: PWA uses the ICM `/token` REST endpoint to retrieve user token, every anonymous user will get a anonymous user token, every identity provider has to configure the `oAuthService` with information about the token endpoint, before expiration the given token should be refreshed.
* reworked authentication documentation structuring after implementation of `/token` API integration * improved documentation regarding ICM authentication, SSO and Punchout Co-authored-by: Silke <s.grueber@intershop.de>
cf49bab
to
3626575
Compare
* reworked authentication documentation structuring after implementation of `/token` API integration * improved documentation regarding ICM authentication, SSO and Punchout Co-authored-by: Silke <s.grueber@intershop.de>
3626575
to
6b11ad1
Compare
Azure Demo Servers are available: |
Further adjustments of the other .md files may follow after having reviewed them as well. |
30f1cea
to
62a1ce2
Compare
I found some more things I could not comment on directly in the files as no changes have been made in the lines in question: migrations.md line 94 says: "The @ngx-translate/http-loader dependency was removed since we did not use it." nginx-startup.md Line 20 says: "- Connect it to the PWA with |
|
* reworked authentication documentation structuring after implementation of `/token` API integration * improved documentation regarding ICM authentication, SSO and Punchout Co-authored-by: Silke <s.grueber@intershop.de> Co-authored-by: MGlatter <m.glatter@intershop.de>
ec9e8fe
to
ad1e8ea
Compare
* old token behavior with the token exchange for each request is replaced by the exchange via token API * get tokens for an anonymous user and for a user with credentials * refresh token before it is expired * revoke token on logout BREAKING CHANGES: PWA uses the ICM `/token` REST endpoint to retrieve user token, every anonymous user will get a anonymous user token, every identity provider has to configure the `oAuthService` with information about the token endpoint, before expiration the given token should be refreshed.
PR Type
[x] Feature
[x] Documentation content changes
What Is the Current Behavior?
The old token behavior with the token exchange for each request, should be replaced by the new token api service.
What Is the New Behavior?
The new token service should be used to authenticate a user. In case the user doesn't login to the PWA, the apiToken for an anonymous user should be used. The apiToken should be automatically refreshed before the token expires.
Does this PR Introduce a Breaking Change?
[x] Yes
Other Information
AB#76575