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.

Sign up for GitHub

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

Jump to bottom

Add client claim to enable explicit configuration of id_token lifetime #373

Closed
nynymike opened this issue Jan 29, 2021 · 2 comments
Closed

Add client claim to enable explicit configuration of id_token lifetime #373

nynymike opened this issue Jan 29, 2021 · 2 comments
Assignees
@yuriyz
Labels
comp-jans-auth-server Component affected by issue or PR comp-jans-cli-tui Component affected by issue or PR effort-1 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality ready-for-triage Issue or PR has sufficient details and it is ready for triage review
Milestone
1.0.21

Comments

@nynymike
Copy link
Contributor

Currently, the lifetime of the id_token is configured globally at the OP level--i.e. the idTokenLifetime attribute in the JSON configuration, applies to all clients available. It would be nice if id_token lifetime could be configured per client. If a client does not have this configuration, it should use the default OP lifetime.

Impacts: ORM, config-API, documentation.
@ghost ghost unassigned HemantKMehta Jan 10, 2022
@ossdhaval ossdhaval transferred this issue from another repository Jan 13, 2022
@ossdhaval ossdhaval added comp-jans-auth-server Component affected by issue or PR comp-jans-cli-tui Component affected by issue or PR effort-1 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality ready-for-triage Issue or PR has sufficient details and it is ready for triage review labels Jan 13, 2022
@moabu moabu added this to the 1.0.4 milestone Nov 3, 2022
@moabu moabu modified the milestones: 1.0.4, 1.0.5 Nov 14, 2022
@moabu moabu modified the milestones: 1.0.5, 1.0.6 Dec 1, 2022
@moabu moabu modified the milestones: 1.0.6, 1.0.7 Jan 9, 2023
@moabu moabu modified the milestones: 1.0.7, 1.0.8, 1.0.9 Mar 1, 2023
@moabu moabu modified the milestones: 1.0.9, 1.0.10 Mar 9, 2023
@yuriyz yuriyz self-assigned this Mar 10, 2023
@moabu moabu modified the milestones: 1.0.10, 1.0.11 Mar 16, 2023
@moabu moabu modified the milestones: 1.0.11, 1.0.12 Apr 5, 2023
@moabu moabu modified the milestones: 1.0.12, 1.0.13 Apr 18, 2023
@moabu moabu modified the milestones: 1.0.13, 1.0.14 May 10, 2023
@moabu moabu modified the milestones: 1.0.14, 1.0.15 Jun 20, 2023
@moabu moabu modified the milestones: 1.0.15, 1.0.16 Jul 12, 2023
@moabu moabu modified the milestones: 1.0.16, 1.0.17 Aug 2, 2023
@moabu moabu modified the milestones: 1.0.17, 1.0.18 Sep 18, 2023
@moabu moabu modified the milestones: 1.0.18, 1.0.21 Nov 22, 2023
@ossdhaval
Copy link
Contributor

Hi @yuriyz

This is an old issue. Could there be any changes in the status?

@yuriyz
Copy link
Contributor

yuriyz commented Dec 5, 2023

It was implemented as part of this ticket #2656

@yuriyz yuriyz closed this as completed Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yuriyz yuriyz

Labels
comp-jans-auth-server Component affected by issue or PR comp-jans-cli-tui Component affected by issue or PR effort-1 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality ready-for-triage Issue or PR has sufficient details and it is ready for triage review
Projects
None yet
Milestone
1.0.21
Development

No branches or pull requests
5 participants
@ossdhaval @yuriyz @nynymike @moabu @HemantKMehta