We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12728

Document setup of LDAP plugin in springboot starter

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • None

      User story

      When I want to use the LDAP plugin with the spring-boot starter project, I can follow a guide so that it becomes easy to get started with the LDAP plugin in the spring-boot starter.

      Background

      Today, customers and community users tend to struggle with setting up the LDAP plugin in the spring-boot starter project.

      Similar to how we document the setup of LDAP when using Tomcat, a dedicated page that describes how to set up LDAP when using the spring-boot starter will help relieve this pain.

      https://docs.camunda.org/manual/7.14/installation/full/tomcat/configuration/

      Hints:

      In SUPPORT-8984, the solution was to add the following beans to the config class in file.name:

       

      // file.name:
      
      @Bean
      public static LdapIdentityProviderPlugin ldapIdentityProviderPlugin() {
        LdapIdentityProviderPlugin plugin = new LdapIdentityProviderPlugin();
        plugin.setServerUrl("ldap://<ldap-address>:389");
        plugin.setManagerDn("cn=Administrator,dc=my,dc=domain,dc=net");
        plugin.setManagerPassword("secret");
        plugin.setBaseDn("dc=my,dc=domain,dc=net");
        plugin.setUserSearchBase("ou=Benutzer");
        plugin.setUserSearchFilter("(uid={0})");
        plugin.setUserIdAttribute("uid");
        plugin.setUserFirstnameAttribute("givenName");
        plugin.setUserLastnameAttribute("sn");
        plugin.setUserPasswordAttribute("userPassword");
        plugin.setGroupSearchBase("ou=Gruppen");
        plugin.setGroupSearchFilter("(member={0})");
        plugin.setGroupIdAttribute("ou");
        plugin.setGroupNameAttribute("cn");
        plugin.setGroupMemberAttribute("member");return plugin;
      }
      

       

      If a user wants to use config properties in their applicaiton.yml, they'd have to map those manually to their configuration class, i.e. by...: 

      // steps to map the config properties in application.yml to the configuration class

        

      Acceptance criteria

       

       

       

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'camunda BPM'
            1. camunda BPM
            2. CAM-12728

            Document setup of LDAP plugin in springboot starter

              • Icon: Feature Request Feature Request
              • Resolution: Unresolved
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • None

                User story

                When I want to use the LDAP plugin with the spring-boot starter project, I can follow a guide so that it becomes easy to get started with the LDAP plugin in the spring-boot starter.

                Background

                Today, customers and community users tend to struggle with setting up the LDAP plugin in the spring-boot starter project.

                Similar to how we document the setup of LDAP when using Tomcat, a dedicated page that describes how to set up LDAP when using the spring-boot starter will help relieve this pain.

                https://docs.camunda.org/manual/7.14/installation/full/tomcat/configuration/

                Hints:

                In SUPPORT-8984, the solution was to add the following beans to the config class in file.name:

                 

                // file.name:
                
                @Bean
                public static LdapIdentityProviderPlugin ldapIdentityProviderPlugin() {
                  LdapIdentityProviderPlugin plugin = new LdapIdentityProviderPlugin();
                  plugin.setServerUrl("ldap://<ldap-address>:389");
                  plugin.setManagerDn("cn=Administrator,dc=my,dc=domain,dc=net");
                  plugin.setManagerPassword("secret");
                  plugin.setBaseDn("dc=my,dc=domain,dc=net");
                  plugin.setUserSearchBase("ou=Benutzer");
                  plugin.setUserSearchFilter("(uid={0})");
                  plugin.setUserIdAttribute("uid");
                  plugin.setUserFirstnameAttribute("givenName");
                  plugin.setUserLastnameAttribute("sn");
                  plugin.setUserPasswordAttribute("userPassword");
                  plugin.setGroupSearchBase("ou=Gruppen");
                  plugin.setGroupSearchFilter("(member={0})");
                  plugin.setGroupIdAttribute("ou");
                  plugin.setGroupNameAttribute("cn");
                  plugin.setGroupMemberAttribute("member");return plugin;
                }
                

                 

                If a user wants to use config properties in their applicaiton.yml, they'd have to map those manually to their configuration class, i.e. by...: 

                // steps to map the config properties in application.yml to the configuration class

                  

                Acceptance criteria

                 

                 

                 

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        andre.bappert Andre
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              andre.bappert Andre
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              3 Start watching this issue

                                Created:
                                Updated: