- ID
- 6faf7141-6e30-4048-b605-51dd69e86cd9
2021-03-10 - Wednesday
Work
DONE [[id:a57fb17d-75fd-417f-a5ed-476027c25552][One-on-One with Andrii]]
CLOSED:
<2021-03-10 Wed 8:45-9:00>
DONE [[id:d0e8b33c-31b9-4f90-a51d-a5f8564c7b6d][SAML/SCIM]] learning
CLOSED:
<2021-03-10 Wed 9:00-9:30>
DONE [[id:f666f784-1570-4f63-aadc-54a5803179c0][Partnership Squad Huddle]]
CLOSED:
DONE [[id:c4cbb750-e46d-42be-ab60-c74e5f5f0cd6][Wednesday Boost]]
CLOSED:
DONE Troubleshoot issues with [[id:ca5573d9-25a9-4e3e-b065-6430f499ae6f][mobile SAML redirects when logging in]]
CLOSED:
DONE Customer call with Emily Bourassa and Medicus IT
CLOSED:
Personal
DONE Reduce sap from [[id:65fd31b2-5dea-4328-886a-10e3af371f71][Maple Tapping Season 2021]]
CLOSED:
Timeline
- Note taken on
Krystian Cybulski during the SAML/SCIM call this week made a specific request that we start look for ways to automate the sort of support we deliver around SAML and SCIM. Interestingly, my mind went towards some sort of a dashboard, but I wonder if there's a way to link the Kibana errors around 400s with specific guidance for the best way to resolve those issues.