You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've deployed Presidio v1 at enterprise scale. We're starting to integrate with other teams internally and I'm showing them around how to use the API. In that exercise I've realized the CRUD calls for Custom Recognizers are open to anyone with access to the API. Have you all considered locking that down in any way? I don't know that we need to go so far as a Kerberos integration, maybe some sort of API Key requirement for those endpoints? Since I'm in need of this functionality, I may be able to contribute a solution to the problem (in v1). If you all have ideas, I'm all ears.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Team,
I've deployed Presidio v1 at enterprise scale. We're starting to integrate with other teams internally and I'm showing them around how to use the API. In that exercise I've realized the CRUD calls for Custom Recognizers are open to anyone with access to the API. Have you all considered locking that down in any way? I don't know that we need to go so far as a Kerberos integration, maybe some sort of API Key requirement for those endpoints? Since I'm in need of this functionality, I may be able to contribute a solution to the problem (in v1). If you all have ideas, I'm all ears.
Regards,
Andrew Mills
Beta Was this translation helpful? Give feedback.
All reactions