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

Allow multiple authentication options for a web app #5442

Open
lachlan-roberts opened this issue Oct 13, 2020 · 4 comments · May be fixed by #12393
Open

Allow multiple authentication options for a web app #5442

lachlan-roberts opened this issue Oct 13, 2020 · 4 comments · May be fixed by #12393
Assignees

Comments

@lachlan-roberts
Copy link
Contributor

Description

An example was brought up in a post on stackoverflow to use both OpenID and FORM authentication together.

What I would like to achieve is to be able to use both authentication methods at the same time, depending on user preference. Some users may have an OpenID account and log in this way; other users may only have "local" accounts so they should be able to use the FORM authentication method. Each type of user (OpenID/local) may have a different login URL; this is perfectly reasonable.

I have also seen other combinations which have been asked about so could be a good idea to make this a generic mechanism if possible. For example BASIC and FORM authentication.

Another answer on stackoverflow said if you are using Wildfly then its possible to configure multiple authentication mechanisms in web.xml

<auth-method>BASIC?silent=true,FORM</auth-method>

Using this silent basic authentication will be tried first, which is basic authentication that only takes effect if an Authorization header is present. If no such header is present then form authentication will be used instead.

So maybe we could do something similar, or maybe this is achievable using something like JAAS or JASPI.

@lachlan-roberts lachlan-roberts self-assigned this Oct 13, 2020
lachlan-roberts added a commit that referenced this issue Oct 18, 2020
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Oct 26, 2020
… server

Multiple OpenIdConfigurations can be stored on server and one is selected
based on the realm name. This allows an option of multiple configurations
where the webapp selects the configuration it wants.

The OpenIdLoginService is no longer needed to be set. It can be null in which
case the Authenticator creates its own one. It can be set to a different
LoginService such as HashLoginService and then the OpenIdAuthenticator will
wrap that LoginService. Otherwise if a OpenIdLoginService is specifically
set it will be used.

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Oct 26, 2020
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Oct 26, 2020
…cation

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@github-actions
Copy link

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Dec 13, 2021
@lachlan-roberts lachlan-roberts removed the Stale For auto-closed stale issues and pull requests label Dec 14, 2021
@github-actions
Copy link

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Dec 15, 2022
@joakime joakime removed the Stale For auto-closed stale issues and pull requests label Dec 15, 2022
Copy link

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Dec 16, 2023
@sbordet sbordet removed the Stale For auto-closed stale issues and pull requests label Dec 16, 2023
lachlan-roberts added a commit that referenced this issue Aug 15, 2024
…entication options

Signed-off-by: Lachlan Roberts <lachlan.p.roberts@gmail.com>
lachlan-roberts added a commit that referenced this issue Oct 16, 2024
…entication options

Signed-off-by: Lachlan Roberts <lachlan.p.roberts@gmail.com>
lachlan-roberts added a commit that referenced this issue Oct 16, 2024
Signed-off-by: Lachlan Roberts <lachlan.p.roberts@gmail.com>
lachlan-roberts added a commit that referenced this issue Oct 16, 2024
Signed-off-by: Lachlan Roberts <lachlan.p.roberts@gmail.com>
lachlan-roberts added a commit that referenced this issue Oct 16, 2024
Signed-off-by: Lachlan Roberts <lachlan.p.roberts@gmail.com>
Copy link

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Dec 16, 2024
@lachlan-roberts lachlan-roberts removed the Stale For auto-closed stale issues and pull requests label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

3 participants