Guy Halse

That's even better than my suggestion :) But strictly SAML2INT only requires the inclusion of the metadata element; it is a REFEDS best practice to have specific error messages at...

@pradtke I opened the issue as a placeholder so it didn't get forgotten. However, I've not had a chance to look at it in any detail yet. If you've got...

I have a claim2name map largely based on what's in http://schemas.xmlsoap.org/ws/2005/05/identity/Identity_Selector_Interoperability_Profile_V1.5.pdf I say "largely" because I also map some things that don't have X.500/LDAP schema mappings in that document (e.g....

I'm doing things very similar to @jhaar, and thought it might be useful to share that here. I do basically the same thing for Strict-Transport-Security, X-Content-Type-Options, and X-XSS-Protection. Except I...

@tvdijen well, the security best practices (and corresponding minimal values for Content-Security-Policy) should still be documented. They just won't include unsafe-inline any more :)

This pull request is now referenced from the [REFEDS MFA Profile implementation FAQ](https://wiki.refeds.org/display/PRO/IdP+Product+specific+questions#IdPProductspecificquestions-IrunSimpleSAMLPHPIdP,whattoIneedtodotosupportREFEDSMFAProfile). For that reason, I wanted to note that since the patch was first written there are changes...

@RincewindsHat yes, it does seem to.

I've forward ported this for simplesamlphp 2.0.0-rc2, and the patch is in 554466328f388a6bcc686d5ce6df6f607d1a352f

> I can't seem to cherry-pick that commit.. It's not part of any branch.. What exactly did you do @ghalse ? It's part of the authnContextClassRef branch in ghalse/simplesamlphp, which...

You appear to have moved Sesotho (st) to en_LS. This makes no sense whatsoever since it's not English and the translation isn't from Lesotho. Detailed explanation in #2305, so it's...