Digital Assistant and Mobile

Get Involved. Join the Conversation.

Topic

    Pawan Gupta
    ODA does not persist accessToken, YML needs logic to save?
    Topic posted October 21, 2019 by Pawan GuptaBlue Ribbon: 750+ Points, tagged Conversational AI, Virtual Assistant, VPA 
    15 Views, 1 Comment
    Title:
    ODA does not persist accessToken, YML needs logic to save?
    Summary:
    ODA does not persist accessToken, YML needs logic to save?
    Content:

    I was expecting, ODA to persists the accessToken though realized, it does not, system component OAuth2 would get the accessToken then if we need to persist perhaps we need to put logic in Bot YML, is this correct understanding or I am missing some concepts? 

    Given ODA does not... is user profile a logical option to save the accessToken?

    Comment

     

    • Frank Nimphius

      Hi,

      you save the access token in a dialog flow variable, this then saves if until you reach a return transition or reset the variable. To keep it beyond return transition, you would save it to a user scope variable. Just assign 

      "user.accessToken" 

      to the System.Auth2AccountLink access token property. The to access the token you use ${user.accessToken}. Note that this setting would keep . Note that OAuth2 tokens expire after 1 hour (I think ist the default setting in IDCS)

      Frank