Do they really need separate adapters? I would have thought Atlassian would be smart enough to let you write one auth plugin for all. Would be good to have this in Keycloak for sure. I can add a repo for you and make you admin of the repo. Does keycloak-atlassian-plugin sound right? We already have one for Jenkins (https://github.com/keycloak/jenkins-keycloak-plugin) although I have no clue what state it is in. On Thu, Oct 5, 2017 at 2:55 PM, Vlastimil Elias <velias(a)redhat.com&gt; wrote: > Hi, > > I'm going to implement OIDC/Keycloak SSO adapters for Atlassian SW > like > Jira or Confluence, starting with Jira first. > > My intention is to have full SSO integration there, so keycloak will > be > used for all logins to Jira (jira login page not used in any way), > and > even automatic login on first jira visit if user has SSO session in > keycloak already. I wrote similar stuff for CAS protocol so I > believe it > is possible to implement it. > > Do you think a repo for these adapters (one shared for all of them) > should be hosted in https://github.com/keycloak organization? Or > should > I implement them in independent repo first and move under keycloak > org > later if my implementation will be worth it? > > I plan to use OIDC adapter from keycloak project for my > implementation, > but my intention is to write them as universal OIDC adapters, not > bound > to Keycloak SSO server itself. > > Vlastimil > > > -- > Vlastimil Elias > Principal Software Engineer, Middleware Engineering Services > Red Hat > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev