Hi Albin, welcome to the forums.
At this time no, there is not an endpoint for approving/disapproving Four-eyes authorization requests via Powershell.
May I ask the use case? The actions requiring Four-Eyes authorization should be reviewed before approving, and I'm just not sure I understand the workflow you would be using with Powershell automation, especially since any script would potentially be a vector for malicious activity, so just hoping you can elaborate on your intended workflow.
With console features like Multi-Factor authentication ( MFA ) would help with protecting against malicious actors being able to just log in and authorize their own deletions, so I'm just not sure I'm understanding how a safe workflow would look for this, but perhaps you can explain your idea a bit more on how you'd envision your powershell script working if it could approve Four-Eyes authorization events.
Thanks!
At this time no, there is not an endpoint for approving/disapproving Four-eyes authorization requests via Powershell.
May I ask the use case? The actions requiring Four-Eyes authorization should be reviewed before approving, and I'm just not sure I understand the workflow you would be using with Powershell automation, especially since any script would potentially be a vector for malicious activity, so just hoping you can elaborate on your intended workflow.
With console features like Multi-Factor authentication ( MFA ) would help with protecting against malicious actors being able to just log in and authorize their own deletions, so I'm just not sure I'm understanding how a safe workflow would look for this, but perhaps you can explain your idea a bit more on how you'd envision your powershell script working if it could approve Four-Eyes authorization events.
Thanks!
Statistics: Posted by david.domask — Aug 23, 2024 12:33 pm
