Cisco APIC Security Configuration Guide, Release 6.2(x)
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Cisco APIC Security Configuration Guide, Release 6.2(x)
Updated: April 17, 2026
Want to summarize with AI?
Log in
On this page
Describes RSA Secure ID authentication and its token-based password creation capabilities.
RSA Secure ID authentication is an authentication method that provides a token which can be used in combination with a fixed key in many different ways to create the password, and supports both hardware and software tokens.
Configure APIC to enable RSA authentication access for secure user authentication and authorization through the RSA server integration.
This task is performed when you need to integrate APIC with an RSA server for enhanced authentication security in your ACI fabric environment.
The ACI fabric is installed, Application Policy Infrastructure Controllers (APICs) are online, and the APIC cluster is formed and healthy.
The RSA server host name or IP address, port, authorization protocol, and key are available.
The APIC management endpoint group is available.
Follow these steps to configure APIC for RSA access using the GUI:
In the APIC, create the RSA provider.
For configuring a RSA provider, see Create a provider.
Create the Login Domain for RSA.
For the detailed procedure, see Create login domain using the GUI.
The APIC is now configured with RSA provider and login domain, enabling RSA authentication access for users.
This completes the APIC RSA configuration steps. Next, configure the RSA server.
Need help?
(Requires a Cisco Service Contract)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.