rr-wfm / identityserverconfig Goto Github PK

Userstory:
As a developer, I want to be able to delete a client secret so that unused secrets are not stored unnecessarily.

Acceptance criteria:

• The developer must be authorized to delete a secret.
• The expiration date of the secret must be set to the current date
• There must be confirmation before the secret can be deleted
• The status of the secret must indicate "expired".

Userstory;
As a developer, I want to be able to revoke a reference token so that it can no longer be used.

Acceptance criteria:

• The developer must be authorized to revoke the reference token.
• The expiration date of the token must be set to the current date.
• There must be a confirmation before the token can be removed.
• The status of the reference token is set to "expired".

Userstory:
As a developer, I want to check a reference token for validity so the client knows if the token is still working.

Acceptance criteria:

• The developer must be authorized to verify the reference token.
• The clientid and reference token must be provided for verification
• The application must indicate a positive response if the reference token is valid in combination with the clientid
• The application must indicate a negative response with the message that it has expired if the reference token has expired
• The application must indicate a negative response if the reference token is not valid in combination with the clientid
• The expiration date of the token must be visible.
• The creation date of the token must be visible.

Userstory:
As a developer, I want to be able to view all the reference tokens so I can check the tokens that currently are in use.

Acceptence Criteria:

• The developer must be authorized to view the reference tokens.
• The ClientId associated with the reference token is visible.
• The creation date of the reference token is visible.
• The expiration date of the reference token is visible.
• The status of the reference token is shown based on the expiration date.

User Story:
As a developer, I want to keep logs of changes made so I know who made the changes.

Acceptance criteria:

• The username of the user that preformed the changes must be stored.
• The time when the changes were made must be saved.
• The item the changes were made to should be saved.

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.