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

Add audience advice #3

Merged
merged 6 commits into from
Oct 15, 2020
Merged

Add audience advice #3

merged 6 commits into from
Oct 15, 2020

Conversation

bbockelm
Copy link
Contributor

Add in some audience advice based upon the discussions at the WLCG JWT hackathon.

@andreaceccanti @paulmillar

Add in some audience advice based upon the discussions at the WLCG JWT hackathon.
@msalle
Copy link

msalle commented Mar 17, 2020

Probably also need to update the text in the table, in particular, remove the

we do not currently provide specific guidance on selecting audience names.

Given condor.example.com is a hostname here, we should make it part of the URI's authority section.
Despite the fact there are cases where one cannot derive the audience from the URL for all redirects (CMS's AAA system is a good counter-example), this should work for all storage system implementations I know of.
@bbockelm
Copy link
Contributor Author

@hannahshort - can we bring this up at the next working group meeting? I would very much like to get this PR resolved so I can cross it off my TODO list...

Ensure it's clear additional audiences are acceptable.
@hannahshort hannahshort merged commit 1e4954a into master Oct 15, 2020
@hannahshort hannahshort deleted the bbockelm-audience-advice branch April 1, 2021 15:06
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

Successfully merging this pull request may close these issues.

6 participants