Question: User logged in as '(null)' externally, but has a cookie as .... invalidating session
0
Jeremy Leipzig • 50 wrote:
I can't upload files to Galaxy - tried logging out, deleting cookies, purging histories.
I am using LDAP authentication.
galaxy.web.framework.webapp WARNING 2015-10-28 16:01:13,951 User logged in as '(null)' externally, but has a cookie as 'leipzigj@email.chop.edu' invalidating session
galaxy.web.framework.decorators ERROR 2015-10-28 16:01:13,975 Uncaught exception in exposed API method:
Traceback (most recent call last):
File "/home/cbmi_bioinf/galaxy-python/galaxy-dist/lib/galaxy/web/framework/decorators.py", line 140, in decorator
rval = func( self, trans, *args, **kwargs)
File "/home/cbmi_bioinf/galaxy-python/galaxy-dist/lib/galaxy/webapps/galaxy/api/tools.py", line 235, in create
target_history = self.history_manager.get_owned( decoded_id, trans.user, current_history=trans.history )
File "/home/cbmi_bioinf/galaxy-python/galaxy-dist/lib/galaxy/managers/secured.py", line 93, in get_owned
return self.error_unless_owner( item, user, **kwargs )
File "/home/cbmi_bioinf/galaxy-python/galaxy-dist/lib/galaxy/managers/secured.py", line 103, in error_unless_owner
raise exceptions.ItemOwnershipException( "%s is not owned by user" % ( self.model_class.__name__ ) )
ItemOwnershipException: History is not owned by user
ADD COMMENT
• link
•
modified 3.1 years ago
by
Dannon Baker ♦ 3.7k
•
written
3.1 years ago by
Jeremy Leipzig • 50
Hi Jeremy
This rings a bell.... I am in the process of 'activating' the API (i.e. making the corresponding changes in the apache config to allow the API calls going through) on one of our servers with LDAP authentication. And I am running into similar issues. Dannon and I are currently looking into the problems
Based on previous posts from you, I assume you are also allowing the API calls to go through?
Sorry, no solution yet (but hopefully soon)
Hans-Rudolf
if I explicitly set
RequestHeader add REMOTE_USER leipzigj
it works, so apparently %{AUTHENTICATE_sAMAccountName}e isn't working anymore. Maybe this is a not a galaxy problem?
The pull request linked below should resolve the issue of null REMOTE_USER headers.