Google Apps using Shibboleth

[Prasanna]

Dear Chris/Paul,

I made changes as you mentioned....Please find the changes below,

*Attribute filter*

<afp:AttributeFilterPolicy id="google.com/a/imperoidm.com"> 
         <afp:PolicyRequirementRule
xsi:type="basic:AttributeRequesterString" value="google.com/a/imperoidm.com"
/> 
         <afp:AttributeRule attributeID="principal"> 
             <afp:PermitValueRule xsi:type="basic:ANY" /> 
         </afp:AttributeRule> 
</afp:AttributeFilterPolicy> 

      

<afp:AttributeFilterPolicy id="google.com/a/imperoidm.com"> 
         <afp:PolicyRequirementRule xsi:type="basic:NOT"> 
                 <basic:Rule xsi:type="basic:AttributeRequesterString"
value="google.com/a/imperoidm.com" /> 
         </afp:PolicyRequirementRule> 
         <afp:AttributeRule attributeID="transientId"> 
             <afp:PermitValueRule xsi:type="basic:ANY" /> 
         </afp:AttributeRule> 
</afp:AttributeFilterPolicy>

*Relying Party*

<rp:RelyingParty id="google.com/a/imperoidm.com"
provider="https://dc01.imperoidm.com/idp/shibboleth"
defaultSigningCredentialRef="IdPCredential">
	<rp:ProfileConfiguration xsi:type="saml:SAML2SSOProfile"
encryptAssertions="never" encryptNameIds="never" />
</rp:RelyingParty>

*google metadata*

<EntityDescriptor entityID="google.com/a/imperoidm.com"
xmlns="urn:oasis:names:tc:SAML:2.0:metadata">
	<SPSSODescriptor
protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
	
<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameidformat:unspecified</NameIDFormat>
		<AssertionConsumerService index="1"
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
		Location="https://www.google.com/a/imperoidm.com/acs" />
	</SPSSODescriptor>
</EntityDescriptor>

<http://shibboleth.1660669.n2.nabble.com/file/n7583468/1.jpg> 


*IDP error log*

18:08:48.089 - INFO [Shibboleth-Access:74] -
20121203T180848Z|172.16.0.26|dc01.imperoidm.com:443|/profile/SAML2/Redirect/SSO|
18:08:48.370 - WARN
[org.opensaml.saml2.binding.encoding.BaseSAML2MessageEncoder:134] - Relay
state exceeds 80 bytes, some application may not support this.
18:08:48.385 - INFO [Shibboleth-Audit:989] -
20121203T180848Z|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect|lbcpkepbdacdjdjlgbihocjnlaeiefhmdfjckbnp|google.com/a/imperoidm.com|urn:mace:shibboleth:2.0:profiles:saml2:sso|https://dc01.imperoidm.com/idp/shibboleth|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|_523a530f2027955a7128b13f5b400f76|raj|urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport|transientId,eduPersonScopedAffiliation,eduPersonTargetedID.old,eduPersonTargetedID,||_b5fccd6f4364433fa06e47578ea49ea1,|

But still I get the same error, the account could not parse the login
request....


Thanks
Prasanna



-----
Prasanna V B
--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Google-Apps-using-Shibboleth-tp7583436p7583468.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.