- ID
- fefd87a6-eb8c-43be-9b4e-c28d03ff194b
2020-12-08 - Tuesday
[[id:ac376401-a8b9-45c5-ab1a-4a77837bd03c][Partnership Squad Engineering Stand-up]]
<2020-12-08 8:30-8:50>
[[id:fa1bef7b-2ac9-47bf-81fe-124b03cb56ed][CMT December 2020 meeting]]
- Note taken on
+ Gary and Robin were not able to make it
[[id:e1f0844a-1193-4e44-9a8c-688c4858ddf0][15Five Partnership: LearnUpon]]-
[[id:363ac209-f840-46f0-9804-282a6d51d603][Pair Programming Time]] with [[id:38a5f6b8-3600-4224-acf2-7b9497402524][Eric]] and [[id:f57ec7f4-49fa-44c7-a750-6d0747b54bff][Zoltan Gorbe]]
DONE Fix tests in [[id:60e7a054-e7c0-4e2f-a674-a2282a145227][ENG-13099]]
CLOSED:
DONE Explore the [[id:7ab85ceb-8d51-44b2-b161-609cdd4a09a9][LearnUpon API]]
CLOSED:
DONE Investigate [[id:77748b56-ec47-49ee-a13e-1aa936638b57][ENG-13638]]
CLOSED:
- Note taken on
This was a SAML/SCIM issue related to a client with an Azure AD configuration
that was likely not setup correctly.
Validation of the incorrect setup involved grabbing the response from the
metadata URL provided by the client and running it through
`get_certs_from_metadata` utility function and noting that response itself is
malformed. It does not include an `encryption` key as most SAML metadata
responses due. Thus, i believe this to be a configuration error on the user's
end.