Naveed,
I've taken the liberty of adding a subject header.
Are you using a browser on the server, or somewhere else? If it's
similar to v2 then you will need to use a browser running on the server
to access the status URL, or add the IP address of the client machine to
the IdP config somewhere (I don't know off the top of my head where the
documentation is for that, sorry).
You could also use the command line status utility
(idp.home/bin/status.sh or idp.home\bin\status.bat); you would have to
run the command on the IdP server of course.
Sara
On 28/01/2016 17:34, Naveed Hashmi wrote:
> Apologies, the idp process log *also* throws the following ..
>
> 2016-01-28 16:11:25,594 - WARN
> [net.shibboleth.utilities.java.support.security.IPRangeAccessControl:94]
> - Policy shibboleth.IPRangeAccessControl$child#50994a3d: Denied request
> from client address '137.222.250.139'
>
> Naveed
>
>
>
> On 28 January 2016 at 16:24, Naveed Hashmi <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> Hi
>
> I've had a go at installing the latest IdP on a test VM, fronting
> tomcat with apache ... the idp-process log shows the following soon
> after the IdP starts up ..
>
> 2016-01-28 16:11:15,572 - WARN
> [org.opensaml.profile.action.impl.LogEvent:76] - An error event
> occurred while processing the request: AccessDenied
>
> When I access https://idp-url/idp/status, I see a page with the
> following ..
>
> Web Login Service - Access Denied
>
> You do not have access to the requested resource.
>
> Any pointers as to where I've messed up are much appreciated.
>
> Thanks
>
> Naveed
>
>
>
>
--
Sara Hopkins
Support Team
UK Access Management Federation for Education and Research
web: http://www.ukfederation.org.uk/
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
|