Neocase HR and portal apps?

[Mark K. Miller]

On Mon, 15 Aug 2016, Cantor, Scott wrote:

> Well, there are three usuals:

You never cease to amaze me!  Of course, every one of these may easily 
apply to my scenario!!!

> - they don't handle SHA-2 (easy to test)

I see what you're saying about SHA-2.  However, the parenthetical went 
right over my head!  ;-)  I'll guess, though, that you're suggesting I 
just do some customization to do SHA-1 for their SPs and see if they work 
that way.  My searches in the wiki for directions or examples didn't turn 
up anything helpful.

I have my IdP running in v2 legacy mode.  Could you provide a pointer to 
directions/example for doing SHA-1 with a specific SP?

Or, did you have some other testing method in mind that really did go 
completely over my head?  (You do know how easily that's done.)

> - you did a from-scratch rebuild of your attribute resolver config and
> so it's omitting xsi:type now from the <AttributeValue> elements and
> their SP is buggy (easy to test, remove encodeType="false" from the
> encoders)

I didn't do a from-scratch rebuild of my attribute resolver config, but 
what I did will result in that same effect.  The only attribute I send 
these SPs is eduPersonPrincipalName.  I replaced how I previously formed
eduPersonPrincipalName with the big script in the example at the bottom of 
this page:  https://wiki.shibboleth.net/confluence/display/IDP30/ScriptedAttributeDefinition

So, that fits your description.  In this case, though, the parenthetical 
makes complete sense!  I removed encodeType="false" from the encoders and 
gave it a try.  It failed just the same as before.

However, even if this was an issue needing addressed, making this change 
and trying it again isn't really a valid test unless I know we're good on 
the SHA algorithm, right?

> - the SP is just incapable of handling XML properly and is so
> fragile/broken that the differences are enough to break it (screw city)

Oh, plesase, no!

> When something doesn't work, rule out the first two, then let management
> know you've probably got a problem.
>
> -- Scott

Again, and as always, THANK YOU!

Max