Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-dev] jetty+setuid and tmp/work directory

My mission has been trying to run Shibboleth IDP without apache on the front and to switch from Tomcat to Jetty. Finally I've actually  managed to do that. Jetty is started nicely with included init script from package and everything works fine. Init script starts Jetty and user is switched from root to jetty and jetty seems to be listening in port 443 like I've configured, even Shibboleth IDP is deployed nicely and it's there answering to Status queries.

 

Then the problem, which of course is that IDP doesn't work. The reason for it is that all temp files which are created during IDP startup are owned by root and jetty/idp process is owned by user jetty and it doesn't anymore have rights for those temp files. If I modify owner of those temp files to jetty after startup, everything works fine.

 

Hopefully someone could give me a hint is there something to avoid this situation.

 

Environment I am using contains Jetty hightide 7.4.4, RHEL 6.1 and Shibboleth IDP 2.3.0.

 

Br,

Sami Silén


Back to the top