# OpenUnison {#openunison}



## Integrating OpenUnison and Argo CD {#integrating-openunison-and-argo-cd}


These instructions will take you through the steps of integrating OpenUnison and Argo CD to support single sign-on and add a "badge" to your OpenUnison portal to create a single access point for both Kubernetes and Argo CD. These instructions assume you'll be using both Argo CD web interface and command line interface as well as running [OpenUnison 1.0.20+](https://openunison.github.io/).

![OpenUnison Portal with Argo CD](/_media/27c8b1219db8c408f694.png)


## Create an OpenUnison Trust {#create-an-openunison-trust}


Update the below `Trust` object and add it to the `openunison` namespace.  The only change you need to make is to replace `argocd.apps.domain.com` with the host name of your Argo CD URL.  The localhost URL is needed for the cli to work.  There is no client secret used for Argo CD since the cli will not work with it.

```
apiVersion: openunison.tremolo.io/v1
kind: Trust
metadata:
  name: argocd
  namespace: openunison
spec:
  accessTokenSkewMillis: 120000
  accessTokenTimeToLive: 1200000
  authChainName: login-service
  clientId: argocd
  codeLastMileKeyName: lastmile-oidc
  codeTokenSkewMilis: 60000
  publicEndpoint: true
  redirectURI:
  - https://argocd.apps.domain.com/auth/callback
  - http://localhost:8085/auth/callback
  signedUserInfo: true
  verifyRedirect: true
```


## Create a "Badge" in OpenUnison {#create-a-badge-in-openunison}


Download [the yaml for a `PortalUrl` object](https://github.com/argoproj/argo-cd/tree/master/docs/assets/openunison-argocd-url.yaml) and update the `url` to point to your Argo CD instance.  Add the updated `PortalUrl` to the `openunison` namespace of your cluster.


## Configure SSO in Argo CD {#configure-sso-in-argo-cd}


Next, update the `argocd-cm` ConfigMap in the `argocd` namespace.  Add the `url` and `oidc.config` sections as seen below.  Update `issuer` with the host for OpenUnison.

```
apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-cm
data:
  url: https://argocd.apps.domain.com
  oidc.config: |-
    name: OpenUnison
    issuer: https://k8sou.apps.192-168-2-144.nip.io/auth/idp/k8sIdp
    clientID: argocd
    requestedScopes: ["openid", "profile", "email", "groups"]
```

If everything went correctly, login to your OpenUnison instance and there should be a badge for Argo CD.  Clicking on that badge opens Argo CD in a new window, already logged in!  Additionally, launching the argocd cli tool will launch a browser to login to OpenUnison.


## Configure Argo CD Policy {#configure-argo-cd-policy}


OpenUnison places groups in the `groups` claim.  These claims will show up when you click on the user-info section of the Argo CD portal.  If you're using LDAP, Active Directory, or Active Directory Federation Services the groups will provided to Argo CD as full Distinguished Names (DN).  Since a DN containers commas (`,`) you'll need to quote the group name in your policy.  For instance to assign `CN=k8s_login_cluster_admins,CN=Users,DC=ent2k12,DC=domain,DC=com` as an administrator would look like:

```
apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-rbac-cm
  namespace: argocd
data:
  policy.csv: |
    g, "CN=k8s_login_cluster_admins,CN=Users,DC=ent2k12,DC=domain,DC=com", role:admin
```