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

Creating a client secret #5

Open
7 tasks
NvanWeeghel opened this issue May 2, 2023 · 2 comments
Open
7 tasks

Creating a client secret #5

NvanWeeghel opened this issue May 2, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@NvanWeeghel
Copy link
Contributor

NvanWeeghel commented May 2, 2023

Userstory:
As a developer, I want to be able to create a new client secret so I can replace the expired secrets with secrets that still work.

Acceptance criteria:

  • The developer must be authorized to be able to create a secret.
  • It must be possible to enter a description.
  • It must be possible to enter an expiration date.
  • The secret must be created by the application.
  • The secret must be correctly associated with the client.
  • The secret must be visible in the application.
  • The created secret must be shown to the user once.
@NvanWeeghel NvanWeeghel added the enhancement New feature or request label May 2, 2023
@jmezach
Copy link
Member

jmezach commented May 2, 2023

@NvanWeeghel Technically I think there can be multiple active (ie. non-expired) secrets for the same client so this story isn't only to replace an expired secret with a new one. The same functionality can also be used to just generate an additional secret for the same client.

@jmezach jmezach changed the title Creating a secret Creating a client secret May 2, 2023
@jmezach
Copy link
Member

jmezach commented May 2, 2023

@NvanWeeghel I've also updated the title of this story to reflect that this is scoped to client secrets. IdentityServer also has the notion of API Resources which can also have associated secrets, but as far as I'm concerned this story only relates to client secrets. Perhaps we could reuse some of this for API Resource secrets as well, but we'll cross that bridge when we get there.

@jmezach jmezach mentioned this issue May 2, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants