links

Author: yarongol

docs/admin/runai-setup/authentication/authentication-overview.md

@@ -7,39 +7,39 @@ Authentication verifies user identity during login, and Authorization assigns th
 
 Authenticated access is required to use all aspects of the Run:ai interfaces, including the Run:ai platform, the Run:ai Command Line Interface (CLI) and APIs.
 
-## **Authentication**
+## Authentication
 
 There are multiple methods to authenticate and access Run:ai.
 
-### **Single Sign-On (SSO)**
+### Single Sign-On (SSO)
 
 Single Sign-On (SSO) is the preferred authentication method by large organizations, as it avoids the need to manage duplicate sets of user identities.
 
 Run:ai offers SSO integration, enabling users to utilize existing organizational credentials to access Run:ai without requiring dedicated credentials.
 
-Run:ai supports three methods to setup SSO:
+Run:ai supports three methods to set up SSO:
 
-* SAML  
-* OpenID Connect (OIDC)  
-* OpenShift
+* [SAML](sso/saml.md) 
+* [OpenID Connect (OIDC)](sso/openidconnect.md)  
+* [OpenShift](sso/openshift.md)
 
 When using SSO, it is highly recommended to manage at least one local user, as a breakglass account (an emergency account), in case access to SSO is not possible.
 
-### **Username and password**
+### Username and password
 
 Username and password access can be used when SSO integration is not possible.
 
-### **Secret key (for Application programmatic access)**
+### Secret key (for Application programmatic access)
 
 Secret is the authentication method for Applications. Applications use the Run:ai APIs to perform automated tasks including scripts and pipelines based on its assigned access rules.
 
-## **Authorization**
+## Authorization
 
 The Run:ai platform uses Role Base Access Control (RBAC) to manage authorization.
 
 Once a user or an application is authenticated, they can perform actions according to their assigned access rules.
 
-### **Role Based Access Control (RBAC) in Run:ai**
+### Role Based Access Control (RBAC) in Run:ai
 
 While Kubernetes RBAC is limited to a single cluster, Run:ai expands the scope of Kubernetes RBAC, making it easy for administrators to manage access rules across multiple clusters.