Yes, from the Okta UI side of things I’m able to set everything up as needed to connect to AWS accounts. I’m trying to translate that to API calls so we can do this programatically.
For instance, we have a template for AWS that we use in the UI. After creation, the apps API will return something like this (which is what I need to translate into the equivalent Okta Java SDK call):
{
...
"accessibility": {
"errorRedirectUrl": null,
"loginRedirectUrl": null,
"selfService": false
},
"credentials": {
"signing": {
"kid": "..."
},
"userNameTemplate": {
"template": "${source.login}",
"type": "BUILT_IN"
}
},
"features": [],
"label": "...",
"name": "amazon_aws",
"settings": {
"app": {
"accessKey": null,
"appFilter": null,
"awsEnvironmentType": "aws.amazon",
"groupFilter": "aws_(?{{accountid}}\\d+)_(?{{role}}[a-zA-Z0-9+=,.@\\-_]+)",
"identityProviderArn": "...",
"loginURL": "https://console.aws.amazon.com/ec2/home",
"overrideAcsURL": null,
"roleValuePattern": "arn:aws:iam::${accountid}:saml-provider/OKTA,arn:aws:iam::${accountid}:role/${role}",
"secretKey": null,
"secretKeyEnc": null,
"sessionDuration": 43200
},
"notifications": {
"vpn": {
"helpUrl": null,
"message": null,
"network": {
"connection": "DISABLED"
}
}
},
"signOn": {
"audienceOverride": null,
"defaultRelayState": null,
"destinationOverride": null,
"recipientOverride": null,
"ssoAcsUrlOverride": null
}
},
"signOnMode": "SAML_2_0",
"status": "ACTIVE",
"visibility": {
"appLinks": {
"login": true
},
"autoSubmitToolbar": true,
"hide": {
"iOS": false,
"web": false
}
}
}