Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If your IDP supports services of the GÉANT Data Protection Code of Conduct category (all eduID.at IDPs should support that category) and follows our current best current practices documentation and recommendations (e.g. attribute resolution, attribute release) there's nothing extra to do to enable access to student discount platforms via InAcademia.

...

If you insist on not following any of our documentation it's pointless to provide add even more documentation here specifically for those not following our documentation, but here goes anyway:

The entityID of the InAcademia service is https://inacademia.org/metadata/inacademia-simple-validation.xml (which you could also have found out yourself, of course) and you'll at least have to release an affiliation and the affiliation attribute as well as an identifier to the service. The appropriate identifier for such a service is the SAML Pairwise-ID, so release that if you have it. (If you don't, maybe start by following our documentation on how to generate it and then on how to scalably release it, too.) Otherwise the SAML Subject-ID or even an eduPersonPrincipalName would also be acceptable (though less preferred) because InAcademia minimises and pseudonymises any data it hands over to connected merchants anway, anwayas described above.