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

Session termination "requirements" #47

Open
gffletch opened this issue Feb 4, 2025 · 4 comments
Open

Session termination "requirements" #47

gffletch opened this issue Feb 4, 2025 · 4 comments

Comments

@gffletch
Copy link
Contributor

gffletch commented Feb 4, 2025

For mobile apps we'll need to address offline_access scopes requested by the mobile apps as that generally means the issued refresh_token is NOT connected to a "signed in session".

@dhs-BI
Copy link
Contributor

dhs-BI commented Feb 4, 2025

Thanks @gffletch. I think we can add this to the SLx levels as a part of the descriptive text below the table in ipsie-levels.md. If you have suggestions, please author a PR.

@brockallen
Copy link

I know the IPSIE levels doc is meant to be high level right now, but thinking of the actual mechanics... how do you imagine the Identity Service reaching out to ping the mobile/native app? Are you expecting some sort of push plumbing to be in place? Is that the standard here? TIA. :)

@aaronpk
Copy link
Collaborator

aaronpk commented Feb 5, 2025

Right now, OIDC back-channel logout says refresh tokens issued with the offline access scope should not be revoked. We just need to ensure they are revoked in the context of session termination in IPSIE

@brockallen
Copy link

Right now, OIDC back-channel logout says refresh tokens issued with the offline access scope should not be revoked. We just need to ensure they are revoked in the context of session termination in IPSIE

That's easy enough to do at the Identity Service for refresh tokens. But there might still be a lingering access token at the mobile/native app. But yea, I guess this thread was for the offline_access semantic... so I guess that's covered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants