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

SASL: Add support for lazy-loaded properties and event callbacks #82

Open
Tracked by #78
nevans opened this issue Nov 21, 2022 · 0 comments
Open
Tracked by #78

SASL: Add support for lazy-loaded properties and event callbacks #82

nevans opened this issue Nov 21, 2022 · 0 comments
Labels
SASL 🔒 Authentication and authentication mechanisms

Comments

@nevans
Copy link
Collaborator

nevans commented Nov 21, 2022 •
edited

Lazy loading can be used with:

  • password prompts,
  • web browser interactions to acquire/refresh OAuth2 access tokens,
  • KMS lookups
  • audit logs
  • dynamic values that can't be computed until data from the server has been seen.

Eagerly doing these actions can be wasteful, frustrating to the user, or violate security policies.
@nevans nevans mentioned this issue Nov 21, 2022
Draft
35 tasks
nevans added a commit that referenced this issue Dec 21, 2022
@nevans
📚 Update docs for #authenticate, #login, etc...
5343336 
The documentation on these methods is meant to complement a new
SASL::Authenticator base class and new documentation on each of the
individual authenticator classes.  See #78 and #82.

That base class is added in another PR (#78), but the documentation for
these methods can be updated without it.

Also, somehow I misremembered `LOGINDISABLED`: it only applies to
`LOGIN`, not `AUTHENTICATE`!  This fixes that error.
@nevans nevans added the SASL 🔒 Authentication and authentication mechanisms label Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
SASL 🔒 Authentication and authentication mechanisms
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nevans