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

Store and use platform audience #48

Open
michaelwheeler opened this issue Apr 7, 2023 · 1 comment
Open

Store and use platform audience #48

michaelwheeler opened this issue Apr 7, 2023 · 1 comment
Assignees

Comments

@michaelwheeler
Copy link
Collaborator

This value can optionally be provided by the platform, in which case it will be used by the tool when requesting an auth token.

@michaelwheeler michaelwheeler added this to the 1.0 Release milestone Apr 13, 2023
@michaelwheeler michaelwheeler self-assigned this Nov 24, 2023
@michaelwheeler
Copy link
Collaborator Author

When creating a service token for a client_credentials token request, multiple values from the registration are used:

  • The sub property uses the client ID
  • The iss property also uses the client ID
  • The aud property uses a platform-specified value if one has been provided, otherwise it uses the auth token URL

Construction of the service token in pylti1p3 can be seen here:
https://github.com/dmitry-viskov/pylti1.3/blob/d8fa43e1ace2885e84dfa4067f0f7379aaa86826/pylti1p3/service_connector.py#L54-L69

It seems like it should be enough to add an aud field to the LtiRegistration model and ensure that it is used in the to_registration method when available.

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

1 participant