Subject Canonicalization problem

Michael A Grady mgrady at unicon.net
Mon Nov 9 13:06:40 EST 2015


> On Nov 9, 2015, at 10:09 AM, Cantor, Scott <cantor.2 at OSU.EDU> wrote:
> 
> 
>> The downside to that, I guess, is that if that follow-on fails, you don't then have Simple to fall back on. (Maybe Simple becomes an optional "initial c14n flow", analogous to the "initial authn flow", that one can configure? For that matter, could one do that now with just a bit of c14n flow configuration, and not fall back on defining a scripted attribute/data connector dependent on that?)
> 
> I don’t know what you’re suggesting.
> 

I was wondering whether one could wire it to be like one of the options with Apache HTTPD module behavior, where one of the c14n flows succeeding (i.e. Simple) would not stop it from trying an additional C14n flow (attribute). 

--
Michael A. Grady
IAM Architect, Unicon, Inc.



More information about the users mailing list