Configure Google OAuth2 Authentication

You can use Kloudfuse UI through your google account authentication. To enable Google OAuth2, you need to register a new application with Google.

Create Google OAuth2 Keys

1. Go to the Credentials page.

2. Click Create credentials > OAuth client ID.

3. Select the Web application application type.

4. Enter Name (e.g. Kloudfuse)

5. Enter URL of the kloudfuse installation in the Authorized JavaScript Origins. Example: kloudfuse.yourcompany.com

6. Click Create

7. Copy the Client ID and Client Secret from the ‘OAuth Client’ modal

Enable Google Auth in Kloudfuse

1. Create a new secret (say, kfuse-credentials) secret in kfuse namespace of your kloudfuse installation in the following format:

   apiVersion: v1
   data:
     GoogleApiKey: <Client Secret>
     GoogleClientId: <Client ID>
     GoogleDomain: <Google Domain>
     JwtSigningKey: and0c2lnbmluZ2tleQ==
     admin-user: <admin user>
     admin-password: <admin password>
   kind: Secret
   metadata:
     name: kfuse-credentials
   type: Opaque

   1. Replace/add Client ID, Client Secret and google domain - you will need to do base64 encode the Client ID, Client Secret and the google domain. You can also use the admin-user and admin-password fields in the kfuse-credentials secret to change the admin user and password from their default values. These values need to be base64 encoded.

   2. To encode the above values in base64 you can use the following command:

      echo -n <value to be encoded> | base64

   3. kubectl apply -f kfuse-credentials.yaml -n kfuse

2. In the custom_values.yaml file that you used for kfuse helm chart installation, add the following lines:

     auth:
       config:
         AUTH_TYPE: "google"
         AUTH_COOKIE_MAX_AGE_IN_SECONDS: 259200
       auth:
         existingAdminSecret: "kfuse-credentials"
         existingSecret: "kfuse-credentials"

3. Install using the helm command with the custom_values.yaml .

4. For the config to take effect, Restart the auth service using:

   kubectl rollout restart deployment auth

5. You should now see a Google login button (if AUTH_TYPE is set to “google”) on the login page.