Skip to content
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

Capability to Configure Custom KeyStores for All Inbound Authentication Protocols #20564

Open
Binara-Sachin opened this issue Jun 18, 2024 · 0 comments
Assignees

Comments

@Binara-Sachin
Copy link
Contributor

By default, the Primary or Tenant KeyStore is used for operations in the Authentication Flow such as Signing or Encrypting JWT-Tokens, SAML-Assertions, etc.
Currently, a separate KeyStore can be configured for the SAML 2.0 flow for inbound authentication-related functionalities.

[keystore.saml]
file_name = ""
password = ""
type = ""
alias = ""
key_password = ""

For the rest of the protocols, (OAuth 2.0, WS-Federation, WS-Trust) WSO2 Identity Server does not have this capability.

@Binara-Sachin Binara-Sachin self-assigned this Jun 18, 2024
@hwupathum hwupathum moved this to In Progress in Identity Server 7.1.0 Sep 27, 2024
@nilasini nilasini added this to the 7.1.0-m2 milestone Sep 30, 2024
@NipuniBhagya NipuniBhagya modified the milestones: 7.1.0-m2, 7.1.0-m3, 7.1.0-m4 Oct 11, 2024
@nilasini nilasini modified the milestones: 7.1.0-m4, 7.1.0-m5 Oct 25, 2024
@nilasini nilasini removed this from the 7.1.0-m5 milestone Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

3 participants