- Home
- Single Sign-On
- Okta Advanced Server Access
Last updated: Apr 13, 2022
Okta Advanced Server Access
Automate IAM across dynamic server fleets at any scale
Overview
Okta Advanced Server Access extends core Okta IAM capabilities to any cloud infrastructure environment - AWS, GCP, Azure, or on-premises. As an integrated application, Advanced Server Access streamlines local Linux and Windows server account lifecycle management from Okta as the source of truth, and provides a seamless SSO experience for SSH and RDP workflows.
Functionality
Add this integration to enable authentication and provisioning capabilities.
Authentication (SSO)
-
API
-
Event Hooks
-
Inbound Federation
-
Inline Hooks
-
Outbound Federation
-
RADIUS
-
SAML
Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
-
Workflow Templates
-
Workflows Connectors
-
SWA
Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
-
OIDC
OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
-
WS-Federation
Provisioning
-
Create
Creates or links a user in the application when assigning the app to a user in Okta.
-
Update
Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
-
Deactivate
Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
-
Attribute Sourcing
The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
-
Sync Password
Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
-
Group Push
Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
-
Group Linking
Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
-
Schema Discovery
Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
-
Attribute Writeback
When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.
Workflows
Add this application connector to your Okta Workflows,
a no-code interface-driven platform for creating custom workflows using
a library of integrated third-party applications and functions.
Sequence action events together to automate identity-centric business processes.
Okta Advanced Server Access Connector actions
- Custom API Action
- Create Preauthorization
- List Server Enrollment Tokens within a Project
- Update Preauthorization
- Create Project
- List Projects for Team
- Add Group to Project
- Create ASA Group
- Remove an ASA User from an ASA Group
- Update Project
- Read Server Enrollment Token for Project
- Add User to Group
- Create Server Enrollment Token for Project
- Delete Project
- Change Project Properties of Project Group
- Remove Group from Team
Connector
Okta Verified
The integration was either created by Okta or by Okta community users and then tested and verified by Okta.