Closed noahtalerman closed 3 months ago
I think this is very important to prioritize before any of our customers get to the renewal dates for their certs. The linked issue https://github.com/fleetdm/confidential/issues/4479 is an example of this going wrong for us internally.
@roperzh are we able to find the APNs, ABM, and SCEP renewal dates for our managed cloud MDM customers?
This way, we can manually send a reminder.
We still plan on having the feature built at least 1 month prior to macOS MDM launch but would be good to notify customers ahead of time as well.
cc @zayhanlon
@noahtalerman I think we should be able to. To be 100% sure I think we should spend a bit of time with Robert doing a trial with one customer at least.
Heads up @zwass @lukeheath and @roperzh this request was discussed during feature fest last week and didn't make it into the current design sprint.
Hey @marko-lisica I recorded some feedback on UI changes in this Loom video here.
Hey @marko-lisica here are the issues that have the CLI designs for cert expiration:
I just verified that we built these warnings:
Maybe we can borrow similar copy for the UI? Looks like we might need to update the copy for APNs error to be clearer about the consequences: all end users will have to take some action to turn MDM off and back on.
Hey @georgekarrv moving story to "Settled". As we talked about during the Design review, I'm passing the notifications API endpoint design to you.
Plan is to make this a frontend only story and use the following endpoints:
cc @marko-lisica
During design review today, we decided to cut the scope for this feature. We won't implement new Notifications API. For now it will be UI change.
Hey team! Please add your planning poker estimate with Zenhub @ghernandez345 @gillespi314
@marko-lisica / @noahtalerman
Where does the Fleet license expiring fit on this hierarchy? Because it's a global banner, I'm thinking after 3 but before 4. That's what I built, but just wanted to confirm. I was also thinking, before 1 sounded reasonable as well.
Where does the Fleet license expiring fit on this hierarchy? Because it's a global banner, I'm thinking after 3 but before 4. That's what I built, but just wanted to confirm. I was also thinking before 1 sounded reasonable as well.
Hey @RachelElysia, I would say on the global level it should be 4th, and on the host level as well 4th before "warning to turn on MDM". Do you know what's the consequence of an expiring license? Maybe it's more dangerous than ABM token expiration, so I would put it higher in that case.
Do you know what's the consequence of an expiring license? Maybe it's more dangerous than ABM token expiration, so I would put it higher in that case.
@RachelElysia and @marko-lisica IIRC expired licenses have no consequences. We just show a undismissible banner.
So, I agree with Marko's suggestion. I think that's what you were saying too Rachel?
Hey @zayhanlon heads up, this customer request was shipped in Fleet 4.51 🎉
Renewal reminders bloom, Like cherry blossoms in spring, Peace in the workflow.
Goal
Changes
Product
Engineering
Context
QA
Risk assessment
Manual testing steps
Testing notes
Confirmation