google apps integration problem

[Dave Perry]

Having done this recently…

Check in your google apps admin account Security > SSO options, if you have enabled a tickbox called something like ‘issue domain-specific identifier’. I think from that error, you have.

You need to setup the relying party config to match that. Here is ours (until <util:list id="shibboleth.RelyingPartyOverrides"> ):
                                <bean parent="RelyingPartyByName" c:relyingPartyIds="#{{'google.com'}}">
            <property name="profileConfigurations">
                <list>
                        <bean parent="SAML2.SSO" p:nameIDFormatPrecedence="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" p:encryptAssertions="false" />
                </list>
            </property>
        </bean>
Change the ‘google.com’ to match yours.

I will update the wiki with my experiences when I get a chance (will try this week, been meaning to since I figured it all out a few weeks back).

HTH,
Dave
_________________________________________________
Dave Perry
eLearning Technologist, Hull College Group (Monday – Thursday)

Room L34 - Queens Gardens Library
Wilberforce Drive, Queen's Gardens, Hull, HU1 3DG
Extension 2230 / Direct Dial 01482 381930

* Need a fast reply? Try elearning at hull-college.ac.uk<mailto:elearning at hull-college.ac.uk> *

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Mark Nesterovych
Sent: 28 November 2016 14:47
To: users at shibboleth.net
Subject: google apps integration problem

Hello.
I am using shibboleth 3.2.1
There are a lot of articles, describing parts of configuration, and I can not find any describing the whole process. If there is any one somewhere will be grateful for any links to such resources.

At the moment integration shows following errors:
2016-11-28 09:45:29,217 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:293] - Resolving re
lying party configuration
2016-11-28 09:45:29,218 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:305] - Checking if relying party configuration EntityNames[google.com/a/example.com,<http://google.com/a/example.com,>] is applicable
2016-11-28 09:45:29,218 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:310] - Relying party configuration EntityNames[google.com/a/example.com,<http://google.com/a/example.com,>] is not applicable

Following part is from relaing-party.xml

    <util:list id="shibboleth.RelyingPartyOverrides">
         <bean parent="RelyingPartyByName" c:relyingPartyIds="google.com/a/example.com<http://google.com/a/example.com>">
           <property name="profileConfigurations">
               <list>
                   <bean parent="SAML2.SSO" p:nameIDFormatPrecedence="urn:oasis:names:tc:SAML:1.1:nameid-format:uns" p:encryptAssertions="false" />
               </list>
           </property>
       </bean>

    </util:list>

Could somebody gave a glue what is wrong here,  and why such configuration is not applicable.
Thank you.


--
Best regards,
Mark Nesterovych

**********************************************************************
This message is sent in confidence for the addressee
only. It may  contain confidential or sensitive
information.  The contents are not to be disclosed
to anyone other than the addressee.  Unauthorised
recipients are requested to preserve this
confidentiality and to advise us of any errors in
transmission.  Any views expressed in this message
are solely the views of the individual and do not
represent the views of the College.  Nothing in this
message should be construed as creating a contract.

Hull College Group owns the email infrastructure, including the contents.

Hull College Group is committed to sustainability, please reflect before printing this email.
**********************************************************************

TEXT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161128/0f2704df/attachment-0001.html>