Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1592

x509 client certificate Authentication and Authorization support

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Hello,

      within certain organizations it would be very convenient to be able to authenticate users with x509 certificates. I also opened a corresponding request for JIRA (JRA-17795) but it would be also useful to offer this feature through SSO.

      Best Regards,
      Edoardo

            [CWD-1592] x509 client certificate Authentication and Authorization support

            @Rupert: can you please share plugin's name/vendor? Thanks!

            Paul M. Goorskis added a comment - @Rupert: can you please share plugin's name/vendor? Thanks!

            we have a jira plugin doing this now.

            rupert THURNER added a comment - we have a jira plugin doing this now.

            shihab added a comment -

            Unfortunately this is not something we're looking to implement in the near future.

            shihab added a comment - Unfortunately this is not something we're looking to implement in the near future.

            Any updates so far?

            Robert Bennek added a comment - Any updates so far?

            there is two aspects of smart card based login:

            1. take the username out of the certificate or the webcontainer where the application is deployed (j2ee standard "principal"). this needs to be done by every application itself, otherwise it would be considered as security risk for logging in.
            2. store user information (like email), permissions, roles, ... which might be partially retrieved or calculated from information in the certificate as well. crowd would be perfect to hold / synchronzie such information.

            rupert THURNER added a comment - there is two aspects of smart card based login: take the username out of the certificate or the webcontainer where the application is deployed (j2ee standard "principal"). this needs to be done by every application itself, otherwise it would be considered as security risk for logging in. store user information (like email), permissions, roles, ... which might be partially retrieved or calculated from information in the certificate as well. crowd would be perfect to hold / synchronzie such information.

            I have just been asked for this feature by a large European enterprise user currently considering deploying Crowd. Contact me for more information if necessary.

            Sam

            Sam Johnston added a comment - I have just been asked for this feature by a large European enterprise user currently considering deploying Crowd. Contact me for more information if necessary. Sam

              Unassigned Unassigned
              ecausarano Edoardo Causarano [Atlassian]
              Votes:
              7 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: