COmanage Users List

[Paul Caskey <>]

Hi Jeremy-

The IdP is back and seems happy.  It says it has loaded the right metadata 
and is logging a scheduled reload in 5 minutes (as it should).

Please let us know if you have trouble.



On 2/7/17, 10:29 PM, 
"
 on behalf of Paul Caskey" 
<
 on behalf of 
>
 wrote:

    Hi Jeremy-
    
    As you’ve diagnosed, this looks to be a shibb SP metadata problem.
    
    The error at the IdP was:
    2017-02-08 00:19:50,293 - INFO 
[org.opensaml.saml.common.binding.impl.SAMLMetadataLookupHandler:128] - 
Message Handler:  No metadata returned for https://169.229.209.86/registry in 
role {urn:oasis:names:tc:SAML:2.0:metadata}SPSSODescriptor with protocol 
urn:oasis:names:tc:SAML:2.0:protocol
    
    I see metadata for the entityID above, but the IDP is not reloading it 
every 5 minutes as it was told to do.
    
    This IdP is an atypical install and it’s not doing well at the moment and 
I’m having trouble figuring it out (how many tomcat instances does one server 
need?), so it may be flaky for a little bit tonight…
    
    
    
    TTYL
    
    
    
    On 2/7/17, 6:46 PM, 
"
 on behalf of Jeremy Rosenberg" 
<
 on behalf of 
>
 wrote:
    
        I’m not sure if this is the place to seek support but I’m trying to 
test out COmanage Registry R2 V2.
        
        I followed all the steps at:
        
        
https://spaces.internet2.edu/display/TPD/COmanage+Release+2+Documentation
        
        And the VM is running.  I can bring up the UI at https://[IP 
Address]/registry
        
        I click the Login button.
        
        I select TIER Testbed Shibboleth IdP which has this link:
        
        https://[IP 
Address]/Shibboleth.sso/Login?SAMLDS=1&target=ss%3Amem%3A327c412aa271be0ba1a80657242073f24c0bb2b06520c4c80a97cdb2d0410819&entityID=https%3A%2F%2Fidp.testbed.tier.internet2.edu%2Fidp%2Fshibboleth
        
        Which brings up an error page on idp.testbed.tier.internet2.edu
        
        “Web Login Service - Unsupported Request”
        “The application you have accessed is not registered for use with 
this service”
        
        This is after waiting for a long time after registering my SPs, on 
several different days.
        
        I assume I have made a mistake when registering my VM as an SP in the 
testbed IDP.  But I’m not sure how to debug that.
        
        If there is somewhere else I need to go for support on adding my VM 
as an SP to the testbed, please let me know.
        
        Jeremy
        
        P.S. As an aside, someone should clean up the "Configuring the 
COmanage Release" page.  It looks like some bullets were added, but the 
references to earlier steps within the text was not updated.  So now 
references are confusing. For example, Step 2.r. references the certificate 
output in 2.o.  But the certificate output is now described in 2.q.  (I kept 
thinking I missed somekind of output from run.sh script)
        
        
        ====================================================
        Jeremy Rosenberg
        Manager, CalNet Identity and Access Management 
        UC Berkeley