<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Helvetica, Arial, sans-serif">Hi Nov,<br>
      <br>
      I talked with our Android developer team and it's possible to use
      an Authenticator module that is bound to the signing key and hence
      protect the data so that only apps signed with that key can access
      the data.<br>
      <br>
      Thanks,<br>
      George<br>
    </font><br>
    <div class="moz-cite-prefix">On 6/24/18 9:11 PM, matake, nov wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHHppZ8bXq8SsbAn3fBpNSk9WQ14uc_D1Reb5yvXdv=mcPpzTw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Hi,
        <div><br>
        </div>
        <div>In this spec, you are going to use Android Account Manager
          as a credential storage for same vendor apps.</div>
        <div>Is there such feature in the Account Manager?</div>
        <div><br>
        </div>
        <div>I thought all app can request any account type on the
          Android platform if the caller app know the account type
          identifier.</div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2018-06-23 2:30 GMT+09:00 George
          Fletcher via Openid-specs-ab <span dir="ltr"><<a
              href="mailto:openid-specs-ab@lists.openid.net"
              target="_blank" moz-do-not-send="true">openid-specs-ab@lists.openid.net</a>></span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Per the
            notes from Thursday's OpenID Connect working group call,
            here are text and xml formatted version of the Native SSO
            for Mobile apps spec.<br>
            <br>
            Please note, the core text is here but this is no where near
            final. Note that the text for additions for dynamic client
            registration and other IANA registrations are text from the
            "front channel logout" spec. I left the sections there as
            they will likely be needed.<br>
            <br>
            The purpose here is to get the core text in the proper
            format.<br>
            <br>
            Thanks,<br>
            George<br>
            <br>
            <br>
            ______________________________<wbr>_________________<br>
            Openid-specs-ab mailing list<br>
            <a href="mailto:Openid-specs-ab@lists.openid.net"
              moz-do-not-send="true">Openid-specs-ab@lists.openid.<wbr>net</a><br>
            <a
              href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"
              rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openid.net/<wbr>mailman/listinfo/openid-specs-<wbr>ab</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Identity Standards Architect
Verizon Media                     Work: <a class="moz-txt-link-abbreviated" href="mailto:george.fletcher@oath.com">george.fletcher@oath.com</a>
Mobile: +1-703-462-3494           Twitter: <a class="moz-txt-link-freetext" href="http://twitter.com/gffletch">http://twitter.com/gffletch</a>
Office: +1-703-265-2544           Photos: <a class="moz-txt-link-freetext" href="http://georgefletcher.photography">http://georgefletcher.photography</a>
</pre>
  </body>
</html>