GEANT OIDC module

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

GEANT OIDC module

Kicic Sakib

Hi,

I am implementing GEANT OIDC module and following: https://github.com/CSCfi/shibboleth-idp-oidc-extension/wiki/Installing-from-archive

 

Im getting error message in log:

 

2020-01-08 13:32:30,688 - 10.66.1.134 - WARN [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AttributeRequesterEntityAttributeExactPolicyRule:75] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PolicyRequirementRule:_f4b6dd28a48f388960c594b2836b8c97': Could not locate SP metadata context

2020-01-08 13:32:30,689 - 10.66.1.134 - INFO [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AbstractEntityAttributePolicyRule:117] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PolicyRequirementRule:_f4b6dd28a48f388960c594b2836b8c97': No metadata available for the entity, returning FALSE

2020-01-08 13:32:30,690 - 10.66.1.134 - WARN [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AttributeRequesterEntityAttributeExactPolicyRule:75] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PolicyRequirementRule:_a409ac31d27571c706683e58bdf1f103': Could not locate SP metadata context

2020-01-08 13:32:30,690 - 10.66.1.134 - INFO [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AbstractEntityAttributePolicyRule:117] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PolicyRequirementRule:_a409ac31d27571c706683e58bdf1f103': No metadata available for the entity, returning FALSE

2020-01-08 13:32:30,691 - 10.66.1.134 - WARN [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AttributeRequesterEntityAttributeExactPolicyRule:75] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/Rule:_80a0f8c1266a98c801636b0abfe7bb50': Could not locate SP metadata context

2020-01-08 13:32:30,691 - 10.66.1.134 - INFO [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AbstractEntityAttributePolicyRule:117] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/Rule:_80a0f8c1266a98c801636b0abfe7bb50': No metadata available for the entity, returning FALSE

2020-01-08 13:32:30,692 - 10.66.1.134 - WARN [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AttributeRequesterEntityAttributeExactPolicyRule:75] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/Rule:_73e40c122c3bba3ad1dedfde27b587b3': Could not locate SP metadata context

2020-01-08 13:32:30,692 - 10.66.1.134 - INFO [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AbstractEntityAttributePolicyRule:117] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/Rule:_73e40c122c3bba3ad1dedfde27b587b3': No metadata available for the entity, returning FALSE

2020-01-08 13:32:30,693 - 10.66.1.134 - WARN [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AttributeRequesterEntityAttributeExactPolicyRule:75] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/Rule:_ba71520de27683bfb20b91087baaa2f0': Could not locate SP metadata context

2020-01-08 13:32:30,693 - 10.66.1.134 - INFO [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AbstractEntityAttributePolicyRule:117] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/Rule:_ba71520de27683bfb20b91087baaa2f0': No metadata available for the entity, returning FALSE

2020-01-08 13:32:30,694 - 10.66.1.134 - WARN [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AttributeRequesterEntityAttributeExactPolicyRule:75] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PolicyRequirementRule:_5bfe30a3acba6f8a3147601fe9d0ddba': Could not locate SP metadata context

2020-01-08 13:32:30,694 - 10.66.1.134 - INFO [net.shibboleth.idp.attribute.filter.policyrule.saml.impl.AbstractEntityAttributePolicyRule:117] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PolicyRequirementRule:_5bfe30a3acba6f8a3147601fe9d0ddba': No metadata available for the entity, returning FALSE

 

Any clue why I am getting this?

 

Regards,


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: GEANT OIDC module

Cantor, Scott E.
On 1/8/20, 8:44 AM, "users on behalf of Kicic Sakib" <[hidden email] on behalf of [hidden email]> wrote:

> Any clue why I am getting this?

Because there is no use of SAML metadata to this point when using OIDC.

-- Scott


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

SV: GEANT OIDC module

Kicic Sakib
Thanks for response.
So i should not care for this errormessage in case when using oidc?
This error thas not have to do with sp running oidc?

Regards,

-----Ursprungligt meddelande-----
Från: users [mailto:[hidden email]] För Cantor, Scott
Skickat: den 8 januari 2020 14:56
Till: Shib Users
Ämne: Re: GEANT OIDC module

On 1/8/20, 8:44 AM, "users on behalf of Kicic Sakib" <[hidden email] on behalf of [hidden email]> wrote:

> Any clue why I am getting this?

Because there is no use of SAML metadata to this point when using OIDC.

-- Scott


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

SV: GEANT OIDC module

Kicic Sakib
Hi again,
What is error bellow meaning:

OpenID Connect Provider error: Error in handling response type

Regards,

-----Ursprungligt meddelande-----
Från: users [mailto:[hidden email]] För Kicic Sakib
Skickat: den 8 januari 2020 15:23
Till: Shib Users
Ämne: SV: GEANT OIDC module

Thanks for response.
So i should not care for this errormessage in case when using oidc?
This error thas not have to do with sp running oidc?

Regards,

-----Ursprungligt meddelande-----
Från: users [mailto:[hidden email]] För Cantor, Scott
Skickat: den 8 januari 2020 14:56
Till: Shib Users
Ämne: Re: GEANT OIDC module

On 1/8/20, 8:44 AM, "users on behalf of Kicic Sakib" <[hidden email] on behalf of [hidden email]> wrote:

> Any clue why I am getting this?

Because there is no use of SAML metadata to this point when using OIDC.

-- Scott


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]