3.9 KiB
2021
2021-W03
2021-01-21 Thursday
IN-PROGRESS code jwt-service work
[2021-01-21 Thu 14:19]
2021-01-22 Friday
| Timestamp | Tags | Headline | Time | |||
|---|---|---|---|---|---|---|
| Total time | 8:56 | |||||
| 2021-01-22 Friday | 8:56 | |||||
| [2021-01-22 Fri 09:52] | work | refacto jwt-service | 8:56 |
IN-PROGRESS refacto jwt-service work
CLOCK: [2021-01-22 Fri 09:53]–[2021-01-22 Fri 18:49] => 8:56
[2021-01-22 Fri 09:52]
- ref
2021-W04
2021-01-25 Monday
MEETING Posture Onboarding work meeting
CLOCK: [2021-01-25 Mon 19:24]–[2021-01-25 Mon 20:02] => 0:38
[2021-01-25 Mon 19:23]
Notes
Martin, Trapani, Didi, Jyoti, Elias, Mirabell, Guillaume
@Martin:
I am a customer of SecureX
Sources (inTune, AMP, Custom, JAMF, Duo, Meraki) Creating the inventory on their behalf. Active AMP, should be onboarded in SecureX.
Onboard device managers, Meraki, etc… Into "my" SecureX Tenant.
Extra credit if we can do this with OAuth2.
Most important make a connection here.
- email exchange.
@Jyoti
@Martin
Vault service and what is authorized between services. APIs underneath
@Didi
webhook to push changes. Ask the vault. Return keys, etc…
We need continuation.
@Didi
Google, trusts, etc…
@Martin
onboarding, revocation,
What about notification?
@Didi that's the idea of continuous data flow. Bidirectional webhooks. Some services will need to have webhooks. Orbital webehook is a very good example.
You go into orbital, you register webhook. And webhook is triggered.
@Elias to Didi
use cases?
@Martin
- continuous flow of data? need to describe use cases.
DONE cleanup jwt extract feedback work
CLOCK: [2021-01-25 Mon 15:04]–[2021-01-25 Mon 19:23] => 4:19
[2021-01-25 Mon 15:04]
DONE refacto JWT extraction reviews work
CLOCK: [2021-01-25 Mon 14:36]–[2021-01-25 Mon 14:51] => 0:15
[2021-01-25 Mon 14:36]
CHAT morning chat issues org work chat
CLOCK: [2021-01-25 Mon 10:00]–[2021-01-25 Mon 12:16] => 2:16
[2021-01-25 Mon 10:16]
- ref