-
Notifications
You must be signed in to change notification settings - Fork 395
Improve searchability of OIDC documents #1728
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
Merged
sberyozkin
merged 1 commit into
quarkusio:develop
from
sberyozkin:well_known_oidc_providers_tags
Jun 20, 2023
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -370,51 +370,51 @@ categories: | |
| - title: Using OpenID Connect (OIDC) to Protect Service Applications | ||
| url: /guides/security-openid-connect | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This URL is the 2.7 state. The 3.1 URL for this guide is: /security-oidc-bearer-token-authentication-tutorial |
||
| description: This guide demonstrates how to use the OpenID Connect extension to protect your Quarkus JAX-RS service application using Bearer Token Authorization where the tokens are issued by OpenID Connect Providers such as Keycloak. | ||
| keywords: sso,jwt,security | ||
| keywords: sso,oidc,oauth2,jwt,security | ||
| - title: Using OpenID Connect (OIDC) to Protect Web Applications | ||
| url: /guides/security-openid-connect-web-authentication | ||
| description: This guide demonstrates how to use the OpenID Connect extension to protect your Quarkus JAX-RS web application using the Authorization Code Flow and OpenID Connect Providers such as Keycloak. | ||
| keywords: sso,security | ||
| keywords: sso,oidc,oauth2,security | ||
| - title: Using OpenID Connect (OIDC) Multi-Tenancy | ||
| url: /guides/security-openid-connect-multitenancy | ||
| description: This guide demonstrates how your OpenID Connect application can support multi-tenancy so that you can serve multiple tenants from a single application. | ||
| keywords: sso,security | ||
| keywords: sso,oidc,oauth2,security | ||
| - title: Using OpenID Connect (OIDC) and Keycloak to Centralize Authorizations | ||
| url: /guides/security-keycloak-authorization | ||
| description: This guide demonstrates how your Quarkus application can authorize access to protected resources using Keycloak Authorization Services. | ||
| keywords: sso,security | ||
| keywords: sso,oidc,security | ||
| - title: Using OpenID Connect (OIDC) and OAuth2 Client and Filters | ||
| url: /guides/security-openid-connect-client | ||
| description: This guide explains how to use OpenID Connect and OAuth2 Client and Filters to acquire, refresh and propagate access tokens. | ||
| keywords: sso,security | ||
| keywords: sso,oidc,oauth2,security | ||
| - title: OpenID Connect (OIDC) and OAuth2 Client and Filters Reference | ||
| url: /guides/security-openid-connect-client-reference | ||
| description: Reference guide for OpenID Connect and OAuth2 Client and Filters. | ||
| keywords: sso,security | ||
| keywords: sso,oidc,oauth2,security | ||
| - title: Configuring Well-Known OpenID Connect (OIDC) Providers | ||
| url: /guides/security-openid-connect-providers | ||
| description: This guide explains how to configure Quarkus to authenticate against well-known OpenID Connect providers such as GitHub, Google, Microsoft, Apple... | ||
| keywords: sso,security | ||
| keywords: sso,oidc,oauth2,github,google,microsoft,apple,facebook,twitter,spotify,security | ||
| - title: OpenID Connect (OIDC) Dev Services | ||
| url: /guides/security-openid-connect-dev-services | ||
| description: Start Keycloak or other providers automatically in dev and test modes. | ||
| keywords: security | ||
| keywords: sso,oidc,security | ||
| - title: Keycloak Admin Client | ||
| url: /guides/security-keycloak-admin-client | ||
| description: Inject a preconfigured Keycloak Admin Client. | ||
| keywords: security | ||
| keywords: keycloak,oidc,security | ||
| - title: Using JWT RBAC | ||
| url: /guides/security-jwt | ||
| description: This guide explains how your application can utilize SmallRye JWT to verify JWT tokens and provide secured access to the JAX-RS endpoints. | ||
| keywords: security | ||
| keywords: jwt,security | ||
| - title: Build, Sign and Encrypt JSON Web Tokens (JWT) | ||
| url: /guides/security-jwt-build | ||
| description: This guide explains how your application can build, sign and/or encrypt JWT tokens with a fluent and configurable SmallRye JWT Build API. | ||
| keywords: jwt,security | ||
| - title: Using OAuth2 RBAC | ||
| url: /guides/security-oauth2 | ||
| description: This guide explains how your Quarkus application can utilize OAuth2 tokens to provide secured access to the JAX-RS endpoints. | ||
| keywords: security | ||
| keywords: oauth2,security | ||
| - title: Using Vault | ||
| url: https://quarkiverse.github.io/quarkiverse-docs/quarkus-vault/dev/index.html | ||
| description: This guide explains how you can use HashiCorp Vault to securely store your credentials in Quarkus. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This title is also obsolete.
The current 3.1 title is
Protect a web application by using OpenID Connect (OIDC) authorization code flow.