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

OIDC support should be on a per-vhost basis #17

Open
youngnick opened this issue Sep 15, 2021 · 1 comment
Open

OIDC support should be on a per-vhost basis #17

youngnick opened this issue Sep 15, 2021 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@youngnick
Copy link
Member

Please describe the problem you have
[A clear, concise, description of the problem you are facing. What is the problem that feature X would solve for you?]
The OIDC support implemented in #13 sets the same config for all vhosts serviced by the authserver installation.

We should consider making it so that the config can be different on a per-vhost basis.
@youngnick youngnick added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 15, 2021
@youngnick youngnick mentioned this issue Sep 15, 2021
Merged
@UXabre
Copy link

UXabre commented Mar 10, 2023 •
edited
Loading

Hi, could somebody help me with how to pass any metadata via the virtual host? I know this hasn't been implemented for the OIDC part but I'm not sure if it is supported to pass any metadata at all? Just to be clear, i'm talking GRPC metadata.

EDIT: yeah... could've searched longer. I'm actually using authPolicy.context to pass any data to my auth backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@youngnick @UXabre