docs: google oauth, okta

packages/noco-docs/docs/140.account-settings/040.authentication/020.google-oauth.md

@@ -5,3 +5,21 @@ tags: ['SSO', 'Google', 'OAuth']
 keywords: ['SSO', 'Overview', 'Authentication', 'Google', 'OAuth']
 ---
 
+NocoDB offers a functionality that allows users to connect with Google OAuth 2.0, enabling them to log into their NocoDB accounts using their Google authentication credentials. This article provides a step-by-step guide to integrating Google OAuth 2.0 with NocoDB.
+
+1. Copy `Redirect URI` from NocoDB
+    - Go to `Account Settings` > `Authentication` > `Google OAuth`
+    - Copy the `Redirect URI` from the `Google OAuth` section
+2. Go to [Google Cloud Console](https://console.cloud.google.com/) and create a new project.
+3. Visit the `OAuth consent screen` within the `APIs & Services` section.  
+    a) Decide on the configuration and registration preferences for your application, specifying the intended user demographic  
+    b) Click on the `Create` button
+4. Set up the OAuth consent screen by providing details about the application and specifying the authorized domains where you host NocoDB.
+5. Proceed to the `Credentials` screen, then click on `Create Credentials`. Choose `OAuth Client ID` from the available options to generate OAuth credentials.
+6. Choose `Web application` from the options available in the `Application type` dropdown menu.
+7. Configure the following  
+    a) `Authorized JavaScript origins` refer to the HTTP origins where your web application is hosted, such as https://app.nocodb.com  
+    b) `Authorized Redirect URIs` refer to the URIs where the user is redirected after successful authentication with Google. Paste the *Redirect URI* copied from NocoDB in step (1). 
+8. Click on the `Create` button to generate the OAuth credentials. Copy the `Client ID` and `Client Secret` from the OAuth 2.0 Client IDs section.
+9. Go to `Account Settings` > `Authentication` > `Google OAuth` in NocoDB and paste the `Client ID` and `Client Secret` in the respective fields.
+

packages/noco-docs/docs/140.account-settings/040.authentication/030.SAML-SSO/010.okta.md

@@ -3,4 +3,28 @@ title: 'Okta'
 description: 'Learn how to configure Okta as an identity provider for NocoDB.' 
 tags: ['SSO', 'Okta', 'SAML']
 keywords: ['SSO', 'Okta', 'SAML', 'Authentication', 'Identity Provider']
----
+---
+
+This article briefs about the steps to configure Okta as Identity service provider for NocoDB
+
+1. Enable `SAML SSO` on NocoDB
+    - Go to `Account Settings` > `Authentication`
+    - Activate `SAML` toggle button
+2. Retrieve `Redirect URI` & `Audience URI` from NocoDB
+    - Go to `Account Settings` > `Authentication` > `SAML`  
+    - Note down `Redirect URI` & `Audience URI`; these information will be required to be configured later with the Identity Provider
+3. Sign in to your [Okta account](https://www.okta.com/) and navigate to the "Get started with Okta" page. 
+   - Click on `Add App` for the Single Sign-On option.
+   - On the `Browse App Integration Catalog` page, select `Create New App`
+4. In the pop-up with title `Create a new app integration` choose `SAML 2.0` as the Sign-in method
+5. On the `Create SAML Integration` page, in the General settings - provide a name for your app
+6. In the `Configure SAML` section:
+   - Enter the Redirect URL in the Single sign-on URL field.
+   - Add the Audience URI in the Audience URI (Entity ID) field.
+   - Choose `Email Address` from the Name ID format options.
+   - Select `Email` from the Application user-name options.
+7. Complete any additional information in the final step (*Optional*) and click `Finish`
+8. On your application's homepage, 
+   - Navigate to the `Sign-on` tab 
+   - Copy the `Metadata URL` from the SAML 2.0 section
+9. Go to the `Assignments` tab and click `Assign` to assign people or groups to this application.