Changing profile/username of the Bot Agent -> change profile/username of Administrator

3 Comments

  • Bryan - Community Manager
    Comment actions Permalink

    Hi Omar,

    The agent represented by the Bot Agent comes from the OAuth token that's used to authenticate.

    While only an admin or owner can create the OAuth client, an OAuth token can be generated by any agent.

    This means that you can log in as a particular agent and follow the instructions in Chat API tutorial: Generating an OAuth token. Since you already have an OAuth client, jump to the "Quickly generating the token with your browser" section to create the OAuth token. Since you're using for the Chat Conversations API, make sure you have read, write AND chat scopes.

    Let me know if I read your question correctly and if the above works for you. Cheers!

    0
  • Bernard
    Comment actions Permalink

    Hi Bryan,

    Thanks for your explanation above. I've also been attempting to understand how to deploy a bot as a user (not agent, admin or owner). I've created an OAuth client as an admin user following the authorisation code grant flow (the resulting token causes the bot to be the admin user). Can you please clarify how I can then use an ordinary user account (the bot) to generate a token than can be subsequently used for Conversation API (and so that we can give the bot a bot name etc) ? Do you mean to log in as the bot user and follow the implicit grant flow ? The only other possibility would be the password grant flow, but this is not available on new accounts any more. The last method, client credentials grant explicitly says it will use the details of the admin who created the client. I asked a question to support and they were quite convinced that registering a bot does not use an "agent seat". I am confused - can you please clarify. Thank you!

    Regards,

    B

     

    0
  • Bryan - Community Manager
    Comment actions Permalink

    Hi Bernard -- apologies for the lack of clarity on this. A Conversations API chat bot does indeed operate under an agent's license. There are no "machine to machine"/client credentials type of agent that can be used. You'll need to create an OAuth token and decide which agent it's created under (doesn't matter how the token is created -- either implicit or authorization code eventually generates a token that will be used in the end).

    Some accounts will create an agent used exclusively for their bot. Some will re-use an existing agent. It's up to you, but either way it's an agent license that's needed. I know this has come up before and there's a desire to have a special license that can be used, but today that's not the case.

    0

Please sign in to leave a comment.

Powered by Zendesk