Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #8483 (closed)

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

Bug: No PUBLIC_SERVER

Reported by: wmoore Owned by: cxallan
Priority: critical Milestone: OMERO-4.4
Component: Web Version: n.a.
Keywords: n.a. Cc: ajpatterson, atarkowska
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: 2012-04-10 (12)

Description

In order to allow access without login, via PUBLIC_USER and PUBLIC_PASSWORD settings, we also need to allow a PUBLIC_SERVER or use localhost by default.

Currently, the login_required get_connection() returns None quite early if there is no server defined:

if server_id is None:
# If no server id is passed, the db entry will not be used and
# instead we'll depend on the request.session and request.REQUEST
# values
    if connector is not None:
        server_id = connector.server_id
    else:
        try:
            server_id = request['server']
        except:
            logger.debug('No Server ID available.')
            return None

We are only logged in via the PUBLIC user if we actually login with a valid server, username and password.

Change History (5)

comment:1 Changed 12 years ago by cxallan

  • Remaining Time set to 0.25

comment:2 Changed 12 years ago by cxallan

  • Status changed from new to accepted

comment:3 Changed 12 years ago by cxallan

  • Remaining Time changed from 0.25 to 0
  • Resolution set to fixed
  • Status changed from accepted to closed

Logic to fix these problems is now on the 8118_share_connection branch:

comment:4 Changed 12 years ago by Chris Allan <callan@…>

(In [2ae66f8d1189eabef9273b6f52e33539916cce9f/ome.git] on branch develop) Reorganised and expanded public user interaction. (See #8443, #8483)

There is now an additional 'omero.web.public.server_id' configuration
option which allows the system administrator to configure the desired
OMERO.server instance to use anonymous / public authentication with.
Furthermore this commit moves the connection retrieval logic into a two
stage process where the retrieval of an "authenticated" connection is
attempted first and if that fails or credentials are missing a "public"
connection attempt is then made.

comment:5 Changed 12 years ago by Aleksandra Tarkowska <A.Tarkowska@…>

(In [14ee811842b60eb6e39130c7dd150fbd16abf02e/ome.git] on branch develop) Reorganised and expanded public user interaction. (See #8443, #8483)

There is now an additional 'omero.web.public.server_id' configuration
option which allows the system administrator to configure the desired
OMERO.server instance to use anonymous / public authentication with.
Furthermore this commit moves the connection retrieval logic into a two
stage process where the retrieval of an "authenticated" connection is
attempted first and if that fails or credentials are missing a "public"
connection attempt is then made.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.68423 sec.)

We're Hiring!