Skip to content

Conversation

@sirosen
Copy link
Member

@sirosen sirosen commented May 12, 2025

[sc-20185]

These were the default for login flows and client credentials. When GlobusApp-driven logins are used, these defaults are not used. They were only applied for direct use of the login flow and token request mechanisms for login clients.

One log line has been changed to produce slightly more useful debug-level logs.

Also, introduce the first v3.x -> v4 upgrading section to the upgrading doc.


📚 Documentation preview 📚: https://globus-sdk-python--1186.org.readthedocs.build/en/1186/

These were the default for login flows and client credentials. When
GlobusApp-driven logins are used, these defaults are not used. They
were only applied for direct use of the login flow and token request
mechanisms for login clients.

One log line has been changed to produce slightly more useful
debug-level logs.

Also, introduce the first v3.x -> v4 upgrading section to the
upgrading doc.
@sirosen sirosen force-pushed the remove-default-scopes branch from 7cd086b to c300c94 Compare May 12, 2025 20:05
Fix typing errors where `... | None` was passed for
`requested_scopes`.

Additionally, to handle cases in GlobusApp, raise usage errors if an
app is ever doing a login without provided scopes in the authorization
parameters. These conditions aren't unreachable based on the types
which are used, but a user who configures things to reach these
conditions is engaged in explicitly unsupported usage (e.g., trying to
give explicit parameters to a client app which don't include scopes).
@sirosen sirosen merged commit 0633eaf into globus:4.x-dev May 12, 2025
7 checks passed
@sirosen sirosen mentioned this pull request Oct 8, 2025
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.

2 participants