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

Cache implementation for inbound authentication #19680

Closed
ldclakmal opened this issue Nov 1, 2019 · 1 comment
Closed

Cache implementation for inbound authentication #19680

ldclakmal opened this issue Nov 1, 2019 · 1 comment
Assignees
@ldclakmal
Labels
Points/5 Equivalent to five day effort Team/StandardLibs All Ballerina standard libraries Type/Improvement
Milestone
Ballerina 1.1.0

Comments

@ldclakmal
Copy link
Member

Description:
This is a subtask of #17652

Currently, JWT inbound authentication has a cache implementation.
All the other inbound authentication schemes (Basic auth, OAuth2, LDAP) should have their own implementation and those should be configured with user inputs.
@ldclakmal ldclakmal self-assigned this Nov 1, 2019
@ldclakmal ldclakmal added this to the Ballerina 1.0.3 milestone Nov 1, 2019
@ldclakmal ldclakmal added the Points/5 Equivalent to five day effort label Nov 1, 2019
This was referenced Nov 1, 2019
Closed
Closed
Closed
@ldclakmal
Copy link
Member Author

Closing this issue since it is divided into few subtasks as referred above.

This was referenced Oct 22, 2020
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ldclakmal ldclakmal

Labels
Points/5 Equivalent to five day effort Team/StandardLibs All Ballerina standard libraries Type/Improvement
Projects
None yet
Milestone
Ballerina 1.1.0
Development

Successfully merging a pull request may close this issue.

Implement cache for inbound authentication ldclakmal/ballerina-lang
1 participant
@ldclakmal