Hi Dave,

Sorry for the late response.

The administrative features of Collectory are already accessible!

The code line "security.cas.uriFilterPattern=/dummy " did not exist in my external config file.

Thanks!!

Cheers.

Daniel Lins

Em 06/03/2014 00:06, <David.Martin@csiro.au> escreveu:
Thanks Daniel.

Did you use the installation script ? If so it should have CAS disabled by default. 

The file:

/data/collectory/config/collectory-config.properties 

should look like:

# Security bypass

security.cas.bypass=true


# disable all security

security.cas.uriFilterPattern=/dummy


Cheers

Dave Martin
ALA
From: ala-portal-bounces@lists.gbif.org [ala-portal-bounces@lists.gbif.org] on behalf of Daniel Lins [daniel.lins@gmail.com]
Sent: 06 March 2014 13:53
To: ala-portal@lists.gbif.org
Subject: [Ala-portal] How to bypass the authentication process of Collectory component

Hi Guys,

We did the deployment of the main ALA components (Biocache, Hubs-webapp and Collectory) and now we do some tests with local data. However, we don't have access to the administrative features of Collectory component. 

We check that the ALA access control is accomplished through the CAS component (Central Authentication Service), and we will install it soon. Now we would like to bypass this authentication in order to test the administrative features without the CAS deployment/configuration. 

I noticed that exist some parameters in the collectory configuration files to do this, but in our tests did not work properly.

Can we disable (bypass) the authentication process to use the collectory administrative features without the CAS deployment? How to do this?

Thanks.

Best Regards,

--
Daniel Lins da Silva
(Cel) 55 11 96144-4050
Research Center on Biodiversity and Computing (Biocomp)
University of Sao Paulo, Brazil