non-default values for policy parameter

Description

Right now the Shibboleth EDS (version 1.1.0) includes this
logic:

if (policy != 'urn:oasis:names:tc:SAML:profiles:SSO:idpdiscovery-protocol:single') {
fatal(getLocalizedMessage('fatal.wrongProtocol'));
return false;
}

I am requesting an RFE for a configuration option, say

this.ignoreNonDefaultPolicy = false;

such that when the option is set to true the EDS would simply ignore
any value for the policy parameter.

The need here is to "mix" or "combine" the EDS with other custom code to make
a single discovery service that does consume and act on other values
for the policy protocol. As such it would be helpful if the "EDS part" of
the discovery service did not fail when a policy parameter is present
but is not the protocol default.

Environment

None

Attachments

1

Activity

Rod Widdowson 
September 28, 2022 at 2:47 PM

closing

Rod Widdowson 
January 31, 2017 at 3:39 PM

This is done. We can reopen it if it doesn't do what ScottK needs.

Rod Widdowson 
January 19, 2017 at 2:11 PM

Giving ScottK another nudge.

I'm ready to call this done, but if you can test it I'd appreciate it.

Rod Widdowson 
January 5, 2017 at 5:23 PM

Scott: Attached should do what you want. If you can easily give it a whirl and let me know I'd appreciate it

I've tested this with a null default and with

this.allowableProtocols = ["urn:oasis:names:tc:SAML:profiles:SSO:idpdiscovery-protocol:single"];

in my config file.

My current plan is to not put anything in the config file and leave this setting in the documentation only.

Rod Widdowson 
January 5, 2017 at 4:00 PM

onto it. Thanks!

Fixed

Details

Assignee

Reporter

Components

Affects versions

Created December 17, 2016 at 11:52 PM
Updated September 28, 2022 at 2:47 PM
Resolved January 31, 2017 at 3:39 PM