Since we in our institution use CAS login of Goobi, we need to use usernames in Goobi workflow that are the same as our usernames that we use for example as unix login and other things.
The users of Goobi workflow get a directory in /home on the server, just like we do for our ssh accounts. The username is the same.
Is there any risk that there will be problems using the same unix login home-dir as is used from Goobi workflow? Do you have any suggestions to change it?
And a question regarding my other forum question,
does the creation of the PDF file (print docket as PDF) save any temporary files in the home directory of the user?
As the linux administrator and goobi user with the same username for both systems I experience issues e.g. when I want to apply to a workflow step in goobi and this step needs access to the filesystem.
We use separate authentification systems for goobi (ldap) and linux (local user). The mismatch was my mistake, when I configured linux, but I have my workarounds.
I have changed both the config settings, and see no change. Is it enough to restart tomcat when you change settings in goobi_config.properties?
Our CAS login is entered as authentication type “openid”. Is that correct? It works to login via CAS.
But then I tested to change home directory in the LDAP / Standard login. When I create a test user with standard login I now get “Could not create user home /var/local/goobi-home/mmmtest”
The settings for the dir are
drwxrwsr-x 4 tomcat tomcat 4096 Aug 25 15:32 goobi-home
Well, I can imagine that some of the upper directories are not writeable for the tomcat user. Please check the permissions from /var or /var/local, too. For testing purposes you could try something like /localhomes, too.
Again: If we don’t find the problem here together we could arrange a call probably.
