-
Notifications
You must be signed in to change notification settings - Fork 22
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
IRS OAuth2 Config - separate credential config for each RestTemplate #378
Labels
hardening
measurements to increase resiliency
Comments
14 tasks
Planning 2:
|
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
…als-config feat(impl):[#378] separate credentials config
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
ds-jhartmann
pushed a commit
that referenced
this issue
Jan 29, 2024
…te-credentials-config Revert "feat(impl):[#378] separate credentials config"
ds-jhartmann
pushed a commit
that referenced
this issue
Feb 7, 2024
ds-jhartmann
added a commit
that referenced
this issue
Feb 7, 2024
…/378-separate-credentials-config Revert "Revert "feat(impl):[#378] separate credentials config""
ds-jhartmann
added a commit
that referenced
this issue
Feb 7, 2024
ds-jhartmann
added a commit
that referenced
this issue
Feb 7, 2024
…737-feature/378-separate-credentials-config Revert "Revert "Revert "feat(impl):[#378] separate credentials config"""
ds-jhartmann
added a commit
that referenced
this issue
Feb 7, 2024
ds-jhartmann
added a commit
that referenced
this issue
Feb 7, 2024
ds-jhartmann
added a commit
that referenced
this issue
Feb 7, 2024
…741-revert-737-feature/378-separate-credentials-config feat(impl):[#378] separate credentials config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As IRS-Administrator,
I want be able to configure a technical user for each service,
so that I am not relying on special technical users.
Hints / Details
With the new Portal, we need to create a Technical User for each System, we interact with. That means that we need a separate User for
spring.security.oauth2.client.registration.common
)spring.security.oauth2.client.registration.common
)spring.security.oauth2.client.registration.portal
)With the current configuration of IRS it is not possible to set a separate User for BPDM Pool, so a change in implementation is required.
Outcome / Acceptance Criteria
Outcome
Acceptance Criteria
Out of Scope
The text was updated successfully, but these errors were encountered: