DavidM.12977 (Customer) asked a question.
Workflow Connectors are passing the wrong user
Since around May, Workflow Connectors changed how it interacts with connected apps. Apps had been seeing Okta as the owner of the Connector but switched to the owner of the Workflow. How do I switch this back?
Example:
I have a Connector for Slack. That connector was created and owned by user "Okta Workflows Machine User".
When a workflow sends a message to Slack, I expect the message to be from the user "Okta Workflows Machine User".
At sometime in May 2022, it started sending the messages from the original author the Workflow.
This is happening for all connectors and all workflows.
Hello David,
I'm not entirely sure what you are referring to a screenshot example of your card configuration and the received message showing the behavior would be helpful.
Just looking at the "Slack - Send Message to Channel" I see an option to either set the sender as a Bot or not.
As a Bot the sender of the message defaults to: okta_workflows_bot
Which identically matches the Apps name of okta_workflows_bot.
If I specify the bot name in the card it can be what ever I want.
Here is an example of (Bot on, Bot off, Bot on & specific name specified)
Thank you. Changing the sender to a Bot. Took care of Slack. But I am still stuck related to Google Worksheet - Create a Row. I want the work flow to interact with the Worksheet as "Okta Workflows Machine User" which is the user who created the Connection. I don't want to create rows in a Google Worksheet as the Workflow Author "Scott Mitchell". If I leave the organization I don't my developer user account to continue. If someone researches the logs I want it to show that Okta Workflows is the source. I don't want them to contact me.
That is going to be determined by the connection created for the Application (Gsheet's in your example). If you are the user authorizing the connection it is going to utilized those credentials to perform an action. Your only real option in this scenario would be to create a "Google Service Account" and create the connection with it. This would use up an additional Google license.
Okta Connections was created by a google service account which was created for this purpose.