Closed mattbasta closed 11 years ago
@mattbasta - I believe this has been taken care of already - #3334
Oh, very cool. Keeping this open for documentation.
mattbasta, is this going to be for 1.1 or later? I am hotly focused on 1.0 docs right now.
I don't think custom origins are available in 1.0, so it can wait until then.
On Mon, Jun 3, 2013 at 9:40 PM, markgif notifications@github.com wrote:
mattbasta, is this going to be for 1.1 or later? I am hotly focused on 1.0 docs right now.
— Reply to this email directly or view it on GitHubhttps://github.com/mozilla/browserid/issues/3481#issuecomment-18888848 .
this should be fixed in code that landed in #3334, please review the change and re-open if it doesn't solve the app://
problem!
Does documentation exist for using custom origins with persona? On Jun 6, 2013 9:52 AM, "Lloyd Hilaiel" notifications@github.com wrote:
this should be fixed in code that landed in #3334https://github.com/mozilla/browserid/issues/3334, please review the change and re-open if it doesn't solve the app://problem!
— Reply to this email directly or view it on GitHubhttps://github.com/mozilla/browserid/issues/3481#issuecomment-19058365 .
I'm not familiar with the Persona docs, which are here: https://developer.mozilla.org/en-US/docs/Mozilla/Persona I think Will Bamberg handles them. Since custom origins were just implemented, I doubt the Persona docs talk about them. Do you have any info on how to do it, I can help.
Support for custom origins has landed:
https://bugzilla.mozilla.org/show_bug.cgi?id=852720
If this seems sane, we should start talking about getting app://-scheme audiences verifiable. The docs for Persona and for packaged apps should also be updated to reflect how to specify an origin for a packaged app in order to take advantage of Persona.
It might be a good idea to reject audiences in the form app://{guid} (as packaged apps are/have been) to prevent developers from abusing the audience.
cc @cvan, @markgif (for docs)