sorry for the late response, I’ve been busy with
I like the idea of saving the “templates”, you are not the first one who came up with this idea, and seems to me that a lot of users would benefit from such a feature. So my thoughts about this are definitively positive, question is who’s going to do this, it’s not going to be a small feature to implement, but I’d be glad to help and give my insights
Just a few points from my side:
- Naming it templates might not be the best idea, it can confuse users with (provisioning) templates that we used for the registration and host initial configuration. Something like registration parameters would be more suitable IMHO.
- Saved entries would be saved per user or the whole organization?
If you set the “token expiry” to unlimited, the token is valid forever but its
- not possible to view which token/entries exists
- not possible to delete old token/entries
Am I right?
Yes, you are right. It is a security issue however it’s not enabled by default, users have to select the unlimited option manually, therefore taking responsibility for the security.
Plus the scope of the token is limited to registration only, you can’t use it in other API endpoints.
Idea: would it be better to generate the tokens from the foreman anonymous account and add an option, to reset the secret so that all tokens are invalid?
Or we can new feature
Invalidate JWT tokens where you can invalidate tokens for the specific user or all of them.
If you want we can schedule a meeting and discuss all the stuff and ideas, there is a lot of space for improvement and we could plan some organized effort to improve the registration feature.