Authenticators are a secure way to broker trust between different applications for the purpose of exchanging secrets and managing authorizations and related functions. Segura® Platform provides integration with the most used authenticators, as described in the following section.
OAuth 1.0 Authenticator
OAuth 1.0 is an authentication method that consists of using four tokens to identify and authorize an application's access. Always use modern authentication types that guarantee data integrity. The ability to authenticate using OAuth 1.0 exists because legacy applications cannot be updated. We discourage its use.
Configuring OAuth 1.0 Authenticator
To use this authentication method, follow these steps:
- Go to DSM > Application > Application.
- Edit or create a new application and select the OAuth 1.0 authentication method.
OAuth 2.0 Authenticator
OAuth 2.0 is an authentication method that consists of using a client ID and a client secret to request a time-limited token and use it to access Segura® Platform resources.
Configuring OAuth 2.0 Authenticator
To use this authentication method, follow these steps:
- Go to DSM > Application > Application.
- Edit or create a New application and select the OAuth 2.0 authentication method.
- Fill the Client ID and Client Secret fields with the values provided by your OAuth 2.0 provider.
- To finish, go to DSM > Application > Application.
When a resource needs to use a secret, it can use its OAuth 2.0 clients to request an
time limited token and use it to request the information from Segura® Platform. If the token used is valid, Segura® Platform will leave the application interacting with DSM secrets and authorizations.
AWS Authenticator
Segura® Platform AWS Authenticator offers a way for AWS users and resources to authenticate with Segura® Platform to access secrets managed by solution.
Configuring AWS Authenticator
Step 1
Create a user on AWS IAM service as described in the AWS documentation.
Step 2
Create a role with the AdministratorAccess policy as described in the official documentation.
Step 3
Configure AWS as an authenticator in Segura® Platform:
- Go to Settings > Authentication > Providers.
- Click on the options button and select New provider.
- On the screen, select the AWS option and provide the AWS Access Key ID and AWS Secret Access Key.
- To finish, go to DSM > Application > Application.
When a resource needs to use a secret, it can use its AWS access keys to request the information from Segura® Platform. Segura® Platform will validate the given access key with AWS and map the policies attributed to the requester. If the data used is valid, Segura® Platform will leave the application interacting with DSM secrets and authorizations.