Grouper Users - Open Discussion List

["GW Brown, Information Systems and Computing" <>]

Hi Richard,

Glad the Admin UI is working.

Another thing the CAS contribution does is 'remove' the default security 
constraints from web.xml. It does this by replacing them with:

 <security-constraint>
   <web-resource-collection>
     <web-resource-name>UI</web-resource-name>
     <url-pattern>/grouperUi/app/*</url-pattern>
   </web-resource-collection>
        <user-data-constraint>NONE</user-data-constraint>
 </security-constraint>

 <security-constraint>
   <web-resource-collection>
     <web-resource-name>UI</web-resource-name>
     <url-pattern>/grouperUi/appHtml/*</url-pattern>
   </web-resource-collection>
        <user-data-constraint>NONE</user-data-constraint>

 </security-constraint>

The 403 error may indicate that part of the Lite UI machinery is trying to 
load a local file through http and falling foul of the default security 
constraint. Hopefully changing / removing the constraints will solve the 
problem.

Gary

--On 04 February 2010 09:36 -0500 

 wrote:

> Hi,
>
> Thanks for pointing that out Gary, that has solved the problem with the
> Admin UI, we can now successfully authenticate straight through to the UI
> as required.
>
> For the Lite UI, I have had a look at the grouper error log for any
> entries when trying to access the Lite UI, the only error we seem to
> catch from groupers perspective is;
>
> 2010-02-04 14:17:51,471: [TP-Processor6] ERROR
> PopulateErrorAction.execute(70) - Caught '403' for
> /grouper/grouperUi/appHtml/grouper.html
>
> I have set the logging to catch everything at the moment. We have been
> looking around the code ourselves to try and work out why its behaving
> like it is, but so far a bit of a loss.
>
> Thanks
>
> Richard



----------------------
GW Brown, Information Systems and Computing