gluu-server by default don't allow to log in new users until admin explicitly allow them login. But it has flexible tool to to customize this behavior. In order to active users by default you should log into oxTrust (identity) as administrator. And do next: - Open "Manage Custom Scripts" - Select "User Registration" tab - Change property "enable_user" value from 'false' to 'true' - Select "Enabled" checkbox - Click "Update" button - Try to register new user after 30 seconds. During this time identity should load this script. This is default simple custom registration script. You can update it if needed.

Hi, Dieter. All user entries are stored under "ou=people" in the Gluu's internal LDAP directory. Setting attribute `gluuStatus` of an user entry to "active" should do the trick. Feel free to report any further issues here. Regards, Alex.

Wow, thanks for the quick answers. @Yuriy: very good, this would be really easy :) @Aliaksandr: I am still confused because I do not see this attribute in the GUI "users" section, or even in Configuration > Show all attributes. Do I have to use a separate LDAP browser to modify that attribute or is there a way in the identity-GUI? Thanks

> Do I have to use a separate LDAP browser to modify that attribute or is there a way in the identity-GUI? Yes, unfortunately you'll need to modify LDAP directory directly, using either console tools in `opendj/bin` (ldapsearch/ldapmodify) or GUI browsers like jxplorer. But it seems Yuriy's answer will resolve your issues anyway, so you shouldn't be bothered with it to much, perhaps.

I find small issue. There is no gluuStatus definition in default install. Can you import this attribute definition to your ldap: [gluuStatus definition](https://github.com/GluuFederation/community-edition-setup/commit/81dcedefd441c14e882ddc59845b58b780b9af0d) Please replace '%(inumOrg)s' with orgInum. You can take it from any other attribute from /install/community-edition-setup/output/attributes.ldif file

Here is sample user entry without enabled registration script: ``` dn: inum=@!FA20.AE26.51A3.7DBF!0001!96B0.78F5!0000!CA3A.16D1,ou=people,o=@!FA20. AE26.51A3.7DBF!0001!96B0.78F5,o=gluu objectClass: gluuPerson objectClass: ox-FA20AE2651A37DBF000196B078F5 objectClass: top cn: test1 test1 displayName: test1 givenName: test1 iname: *person*test1 inum: @!FA20.AE26.51A3.7DBF!0001!96B0.78F5!0000!CA3A.16D1 mail: test1@gluu.org oxCreationTimestamp: 20160308132801.393Z sn: test1 uid: test1 userPassword:: xyz ``` This is sample entry with enabled script: ``` dn: inum=@!FA20.AE26.51A3.7DBF!0001!96B0.78F5!0000!0C8C.238A,ou=people,o=@!FA20. AE26.51A3.7DBF!0001!96B0.78F5,o=gluu objectClass: gluuPerson objectClass: ox-FA20AE2651A37DBF000196B078F5 objectClass: top cn: test2 test2 displayName: test2 givenName: test2 gluuStatus: active iname: *person*test2 inum: @!FA20.AE26.51A3.7DBF!0001!96B0.78F5!0000!0C8C.238A mail: test2@gluu.org oxCreationTimestamp: 20160308134052.311Z sn: test2 uid: test2 userPassword:: xyz ``` Second entry has ``` gluuStatus: active ```

OK, solved! Took me a while to figure out the correct connection call though: ``` bin/ldapmodify -Z -p 1636 -D "cn=directory manager" -a -f attribute-gluustatus.ldif ``` (can you put that somewhere in the installation documentation, I did not see it?) Afterwards, I set the user's gluuStatus to "active" and I was able to login. Great support guys, thank you very much!

Dieter, In Gluu Server 2.4.2 version, you can enable/disable new user's registration from oxTrust ( GUI ). By default we are keeping it 'false'. You can make it 'true' if you want. Screenshot attached.