• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • 1.3
    • Directory - LDAP
    • None
    • 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.

      Currently OpenLDAP connector does not support CRYPT. See also CWD-427. Although CRYPT is not recommended as an encryption method any more, some customers might still need it.

      Additional work in this to make sure OpenLDAP password are saved with the correct prefix all the time.

        1. applicationContextEncryption.xml
          2 kB
          angel
        2. CRYPTPasswordEncoder.java
          2 kB
          angel
        3. jcrypt.java
          23 kB
          angel
        4. PasswordEncoderFactory.java
          1 kB
          angel

            [CWD-481] Support CRYPT encryption in OpenLDAP connector

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3389079 ] New: JAC Suggestion Workflow 3 [ 3629513 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1390547 ] New: JAC Suggestion Workflow [ 3389079 ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273296 ] New: Simplified Crowd Development Workflow v2 [ 1390547 ]
            jawong.adm made changes -
            Workflow Original: Feature Request Workflow [ 174002 ] New: Crowd Development Workflow v2 [ 273296 ]
            Justin Koke made changes -
            Workflow Original: jira [ 85393 ] New: Feature Request Workflow [ 174002 ]
            DonnaA made changes -
            Component/s Original: Connector [ 11554 ]

            angel added a comment -

            Hi Justin,

            this is good news indeed. Thanks for letting as know.

            Cheers,
            Aggelos

            angel added a comment - Hi Justin, this is good news indeed. Thanks for letting as know. Cheers, Aggelos

            Hi Aggelos,

            This is my plan, I will be adding in the Atlassian Plugin Framework to Crowd in either 1.3 or 1.4, so after this time we should be able to implement all the encoders as plugins.

            Justin

            Justin Koke added a comment - Hi Aggelos, This is my plan, I will be adding in the Atlassian Plugin Framework to Crowd in either 1.3 or 1.4, so after this time we should be able to implement all the encoders as plugins. Justin

            angel added a comment -

            Hi Dave,

            that was a real blow This way you avoid the support costs but you pass on the maintenance costs to the customer. Every time we (our customer) need to upgrade Crowd, we have to patch the release in order to support the encryption scheme. And the upgrades are not that rare.

            Is there any chance you can make the encryption schemes pluggable in order to develop it as a plugin?

            Regards,
            Aggelos

            angel added a comment - Hi Dave, that was a real blow This way you avoid the support costs but you pass on the maintenance costs to the customer. Every time we (our customer) need to upgrade Crowd, we have to patch the release in order to support the encryption scheme. And the upgrades are not that rare. Is there any chance you can make the encryption schemes pluggable in order to develop it as a plugin? Regards, Aggelos
            David O'Flynn [Atlassian] made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              justen.stepka@atlassian.com Justen Stepka [Atlassian]
              38754ddc40c7 angel
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 12h Original Estimate - 12h
                  12h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 16h
                  16h