Neocase HR and portal apps?

[Mark K. Miller]

On Tue, 16 Aug 2016, Cantor, Scott wrote:

>> And, given that question, in your first message when you said "(easy to
>> test)" were you referring only to native v3 configs, or is there something
>> for me to try that I'm just not grasping?
>
> I was referring to native, yes.

Fair enough!  ;-)

>                                 Converting that file over is a fairly 
> straightforward process even if one doesn't simplify anything in the 
> process, it's a one to one conversion of settings.

Damn, you're good!  I almost included this question in my previous reply, 
but I didn't want to 'pollute' one thread with a variety of questions.  I 
was wondering if there was some 'small scale' way to only convert a 
minimum of "stuff" to address this scenario.

When you say "this file" you're talking about the credentials.xml file, 
right?  And, of course, associated 'tweaks' to the relying-party.xml and 
idp.properties files?

Is that a reasonable approach?  Just keep the changes within that set of 
file to allow for the per-entity configuration flexibility of native v3?

> If they wrote it themselves, I'm sure they could have implemented only 
> SHA-1. No telling what they did, what libraries were used, why they 
> limited it in the first place, if in fact they did.

I just got off the phone with one of the Neocase engineers.  Any/all 
assessment of non-Shibboleth SAML implementations aside, I have to say 
the initial contact with the Neocase engineer was VERY ENCOURAGING!  He 
had reviewed some error logs and was headed in this 'SHA-1/SHA-2' 
direction even before we talked.  Right now he's looking for a new DLL to 
change on that end to get this working again.  He was a pleasure to talk 
with!

Yet another 'personal sanity check' for me, if you don't mind...  Am I 
correct in thinking that turning off signing and encryption for this SP 
would make the SHA-1/SHA-2 difference a moot point?

> -- Scott

Thanks again,

Max