The Okta Authentication Plugin adds support for authentication via Federated Identity and then database access via IAM.
Federated Identity allows users to use the same set of credentials to access multiple services or resources across different organizations. This works by having Identity Providers (IdP) that manage and authenticate user credentials, and Service Providers (SP) that are services or resources that can be internal, external, and/or belonging to various organizations. Multiple SPs can establish trust relationships with a single IdP.
When a user wants access to a resource, it authenticates with the IdP. From this a security token generated and is passed to the SP then grants access to said resource. In the case of AD FS, the user signs into the AD FS sign in page. This generates a SAML Assertion which acts as a security token. The user then passes the SAML Assertion to the SP when requesting access to resources. The SP verifies the SAML Assertion and grants access to the user.
- This plugin requires the following runtime dependencies to be registered separately in the classpath:
- Note: The above dependencies may have transitive dependencies that are also required (ex. AWS Java SDK RDS requires AWS Java SDK Core). If you are not using a package manager such as Maven or Gradle, please refer to Maven Central to determine these transitive dependencies.
- This plugin does not create or modify any Okta or IAM resources. Okta must be federated into to your AWS IAM account before using this plugin. You can follow Okta's integration guide.
Note
Since AWS Java SDK RDS v2.x size is around 5.4Mb (22Mb including all RDS SDK dependencies), some users may experience difficulties using the plugin due to limited available disk size. In such cases, the AWS Java SDK RDS v2.x dependency may be replaced with just two dependencies which have a smaller footprint (around 300Kb in total):
It's recommended to use AWS Java SDK RDS v2.x when it's possible.
Note
AWS IAM database authentication is needed to use the Okta Authentication Plugin. This is because after the plugin acquires SAML assertion from the identity provider, the SAML Assertion is then used to acquire an AWS IAM token. The AWS IAM token is then subsequently used to access the database.
- Enable AWS IAM database authentication on an existing database or create a new database with AWS IAM database authentication on the AWS RDS Console:
- If needed, review the documentation about IAM authentication for MariaDB, MySQL, and PostgreSQL.
- Configure Okta as the AWS identity provider.
- If needed, review the documentation about Amazon Web Services Account Federation on Okta's documentation.
- Add the plugin code
okta
to thewrapperPlugins
value, or to the current driver profile. - Specify parameters that are required or specific to your case.
Parameter | Value | Required | Description | Default Value | Example Value |
---|---|---|---|---|---|
dbUser |
String | Yes | The user name of the IAM user with access to your database. If you have previously used the IAM Authentication Plugin, this would be the same IAM user. For information on how to connect to your Aurora Database with IAM, see this documentation. |
null |
some_user_name |
idpUsername |
String | Yes | The user name for the idpEndpoint server. If this parameter is not specified, the plugin will fallback to using the user parameter. |
null |
[email protected] |
idpPassword |
String | Yes | The password associated with the idpEndpoint username. If this parameter is not specified, the plugin will fallback to using the password parameter. |
null |
someRandomPassword |
idpEndpoint |
String | Yes | The hosting URL for the service that you are using to authenticate into AWS Aurora. | null |
ec2amaz-ab3cdef.example.com |
appId |
String | Yes | The Amazon Web Services (AWS) app configured on Okta. | null |
ec2amaz-ab3cdef.example.com |
iamRoleArn |
String | Yes | The ARN of the IAM Role that is to be assumed to access AWS Aurora. | null |
arn:aws:iam::123456789012:role/adfs_example_iam_role |
iamIdpArn |
String | Yes | The ARN of the Identity Provider. | null |
arn:aws:iam::123456789012:saml-provider/adfs_example |
iamRegion |
String | Yes | The IAM region where the IAM token is generated. | null |
us-east-2 |
idpPort |
String | No | The port that the host for the authentication service listens at. | urn:amazon:webservices |
urn:amazon:webservices |
iamHost |
String | No | Overrides the host that is used to generate the IAM token. | null |
database.cluster-hash.us-east-1.rds.amazonaws.com |
iamDefaultPort |
String | No | This property overrides the default port that is used to generate the IAM token. The default port is determined based on the underlying driver protocol. For now, there is support for jdbc:postgresql: and jdbc:mysql: . Target drivers with different protocols will require users to provide a default port. |
null |
1234 |
iamTokenExpiration |
Integer | No | Overrides the default IAM token cache expiration in seconds | 870 |
123 |
httpClientSocketTimeout |
Integer | No | The socket timeout value in milliseconds for the HttpClient used by the OktaAuthPlugin. | 60000 |
60000 |
httpClientConnectTimeout |
Integer | No | The connect timeout value in milliseconds for the HttpClient used by the OktaAuthPlugin. | 60000 |
60000 |
sslInsecure |
Boolean | No | Indicates whether or not the SSL connection is secure or not. If not, it will allow SSL connections to be made without validating the server's certificates. | false |
true |