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

AspNetCore Multi-Tenant Jwt Bearer Token Configuration #44804

Closed
1 task done
BrianMikinski opened this issue Oct 31, 2022 · 4 comments
Closed
1 task done

AspNetCore Multi-Tenant Jwt Bearer Token Configuration #44804

BrianMikinski opened this issue Oct 31, 2022 · 4 comments
Labels
area-auth Includes: Authn, Authz, OAuth, OIDC, Bearer
Milestone

Comments

@BrianMikinski
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

@HaoK @Tratcher @blowdart

Hi y'all,

I'm trying to configure multiple jwt bearer tokens for authentication in an AspNetCore project.

Currently, I have a solution working based on utilizing a custom IOptionsMonitor. The basic strategy I followed came from this GitHub issue and the subsequent Stack Overflow post.

While this is working, is there a better or more officially supported strategy for multi-tenant jwt bearer token auth? I've also noticed the following multi-tenant auth posts but have yet to see anything canonical from the AspNet team. Thanks in advance for any help or suggestions!

Describe the solution you'd like

Suggested best practices for multi-tenant jwt bearer token auth scenarios.

Additional context

None.

@Tratcher Tratcher added the area-auth Includes: Authn, Authz, OAuth, OIDC, Bearer label Oct 31, 2022
@adityamandaleeka adityamandaleeka added this to the .NET 8 Planning milestone Nov 2, 2022
@ghost
Copy link

ghost commented Nov 2, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@davidfenko
Copy link

davidfenko commented May 11, 2023

Hello @BrianMikinski do you perhaps have the option to share your solution for reference?

Also, I realise this is not an architecture-based solution, but a dynamic JWT handler implementation has been done here.

@BrianMikinski
Copy link
Author

@davidfenko - Unfortunately I do not have a repo I can share but the solution shown athttps://github.com/PoweredSoft/DynamicJwtBearer/tree/master is quite interesting. This may be another version of what we were able to achieve. Thank you for the response

@mkArtakMSFT
Copy link
Member

Thanks for contacting us.
While this may be a great idea, it is not aligned with our long-term vision to make it part of the framework. For many other ideas which don't belong to the framework we encourage the community to build and ship on their own, contributing to the expanding .NET Ecosystem.

You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Feb 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-auth Includes: Authn, Authz, OAuth, OIDC, Bearer
Projects
None yet
Development

No branches or pull requests

6 participants