-
Notifications
You must be signed in to change notification settings - Fork 386
AWS OpenID Authentication
Note: This feature is available in Enterprise, AWS, Team editions only.
AWS-OpenID Authentication uses AWS credentials to authenticate users in applications, leveraging OpenID Connect with AWS IAM. It enables secure, efficient user access control, minimizing separate account management. For comprehensive setup information of AWS OpenID itself, refer to the official AWS OpenID documentation.
-
As an administrator, go to Settings -> Server Configuration.
-
Find the AWS option (in the Configuration section) and AWS OpenID (in the Authentication Settings section). Activate this setting to enable AWS authentication.
Note: In CloudBeaver AWS Edition, the AWS option is enabled by default.
-
Save the changes.
For instructions on configuring AWS Regions, see AWS Settings.
-
As an administrator, navigate to Settings -> Identity Providers.
-
Click on the + Add button.
-
Fill in the following fields:
Field Description Provider Select AWS OpenID
from the dropdown menu.ID Enter a unique identifier for the configuration. Configuration name Enter a descriptive name for this configuration. Description Provide a brief description of this identity provider configuration. Icon URL Enter the URL of an icon to represent this provider. Disabled Leave unchecked to enable this identity provider. Client ID The client identifier provided by the OpenID Connect provider. Client Secret A secret key associated with the client ID for authentication. IDP auth endpoint URL The endpoint for initiating the authentication process. IDP token endpoint URL The endpoint for obtaining access and refresh tokens. Role ARN ARN of the role that will be used by the users during authorization. Important: The Role ARN added during this step acts as the default role. It's not advisable to use an administrator role at this step. It is recommended to use a role with minimum privileges during provider setup. After the provider is configured, you will see an AWS Role ARN field for each user, where you can specify a role with higher privileges, if necessary.
Note: The values for the Client ID, Client Secret, IDP auth endpoint URL, and IDP token endpoint URL depend on the specific OpenID Connect provider being used.
-
Click on the Create button.
-
Copy Redirect and Sign out Links:
- Enter the newly created identity provider.
- Copy the Redirect link and the Sign out link.
-
Update Redirect URIs in the authorization service.
-
With the AWS OpenID configuration now established, proceed to the login screen.
-
Select the Federated authentication method, labeled with the Configuration name you specified.
-
Clicking on this authentication method will redirect you to the Sign in with Google page.
-
After selecting the necessary account, you will be automatically redirected and logged into the CloudBeaver.
-
Verify the Integration of AWS and OpenID
- Once logged in, click on your username in CloudBeaver and navigate to the User Info tab.
- Here, you should see two tokens. Their presence indicates that the integration of AWS and OpenID has been successfully completed, and CloudBeaver has access to the necessary credentials.
- Application overview
- Demo Server
- Administration
- Supported databases
- Accessibility
- Keyboard shortcuts
- Features
- Server configuration
- CloudBeaver and Nginx
- Domain manager
- Configuring HTTPS for Jetty server
- Product configuration parameters
- Command line parameters
- Local Preferences
- Team Edition Overview
- Getting started with Team Edition
- Team Edition Server Configuration
- Projects in Team Edition
- Teams in Team Edition
- Team Edition Deployment
- Roles in Team Edition
- Git integration in Team Edition
- Datasets in Team Edition
-
CloudBeaver Community
-
CloudBeaver AWS
-
CloudBeaver Enterprise
-
Deployment options
-
Development