Omeka - platform for digital cultural heritage web publishing

[jeau]

@girish yes, I asked Julian from Biblibre who who develops this module. He talk me that the current released (0.3.0) of Ldap module I used does not allow to configure the LDAP attributes to retrieve the name and email. I tried from source, it's works partially, I retreive the user mail address but I can sign in only with username, not mail.

[imc67]

@jeau said in Omeka - platform for digital cultural heritage web publishing:

I can sign in only with username

That is no problem at all as app like Wordpress and Nextcloud also uses usernames as login.

[jeau]

@imc67 you're right, it's works with the Ldap module, but usually Omeka S users use their email address and in their profile there's no username.

[girish]

@jeau atleast the login form of omeka s says "email or username".

[imc67]

@girish said in Omeka - platform for digital cultural heritage web publishing:

@jeau atleast the login form of omeka s says "email or username".

Indeed and for me it’s ok. And for the time being as “Unstable” in the AppStore it might be possible to use username as Account name?

[jeau]

@girish I never understood why the form asks for name or email. I didn't submit any changes either.

I just found the module UserNames who solve this issue. I can install it by default.

@imc67 I hope it will be possible soon.

[jeau]

Oups, UserNames module broke ldap access I will report this issue.

[jeau]

@girish I installed some components required for official modules and made some settings and tests. I think we can provide this application as "unstable" in the store. I hope I haven't forgotten anything important.

[nebulon]

@jeau this is great! I've just ran the tests and we are looking good.
I will update the manifest to add things like mediaLinks and such for the appstore and then push it out as unstable later today.

Thanks a lot for the work

[jeau]

@nebulon thank's

About tests. Is there a way to test the ldap connection? For my tests, I could connect with my initial administrator, activate and configure the Ldap module but then how to verify? I can't seriously give a Cloudron login and password inside my test code and repo.

[nebulon]

@jeau I've now pushed it as unstable for a start to collect further feedback.

Regarding the LDAP tests, I have to take a closer look as well how to do that. If you are just concerned about the username/password, then we usually follow the pattern that you run the tests with a USERNAME and PASSWORD env variable locally against a test Cloudron. But since we have the package now in the store, we will test new releases from here on on our test Cloudrons anyways.

[imc67]

@nebulon @jeau I just installed the app from the appstore and discovered after activating the LDAP module indeed as @girish wrote earlier a "strange" username and email.

However after trial and error I succeeded to make it very workable:

The 2 attributes were empty after activating and as you see with just those 2 LDAP attributes is works fine!!

For new users it might be an idea to activate the module on install and fill the fields with those to attributes?

[jeau]

@imc67 thank's for testing.

I mentioned in the documentation that you have to activate and configure the Ldap module manually. But I forgot write this in the postinstall file in order to make this information visible immediately after installation. I just did it.

I'll investigate to activate the module automatically. However I hesitate to operate directly in the database. I'll ask on the Omeka forum

[imc67]

@jeau thanks!!!!

[jeau]

@nebulon I updated the code with this information about the activation and configuration of the Ldap module. On the app store the Forum and Documentation links refer to the same page.

[nebulon]

@jeau thanks, I will publish it then again.

[nebulon]

I will lock this topic in favor of the new forum section for the app at https://forum.cloudron.io/topic/5097/omekas-package-updates