title: How to authenticate with custom apis/microservices from using Twilio Flex SSO token
body: <p>I have successfully enabled a plugin to work with Azure AD . And based on the  documentation I can find, Twilio encourages the idea that if you wanted to communicate from React JS app to custom APIs , then you can do so. The problem I see is that Twilio sort of ignores the fact that when  communicating to those APIs from the client app, authentication must be in place between custom apis and react plugin app</p>
  
  <p>How are people unifying the authentication between the Auth that takes place at the UI later and subsequent requests that are mare to backend apis? Can we reuse the token?</p>
  
  <p>Within the <a href="https://www.twilio.com/console/flex/users/single-sign-on" rel="nofollow noreferrer">https://www.twilio.com/console/flex/users/single-sign-on</a> I see</p>
  
  <p><a href="https://i.stack.imgur.com/i5SZI.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/i5SZI.png" alt="enter image description here"></a></p>
  
  <p>Does this mean OAuth support is coming? Where can I post this question to increase the likelyhood of receiving some indicators as to which protocols are going to be supported in the near future? If twilio flex team is in fact working on adding OAuth support, I would imagine it would only benefit them to let the community know, especially those with existing microservices and OAuth based flow already preconfigured. </p>
  
  <p>Ive added a issue here hopefully to get some response on this question. 
  <a href="https://github.com/twilio/twilio-flex-token-validator/issues/13" rel="nofollow noreferrer">https://github.com/twilio/twilio-flex-token-validator/issues/13</a></p>