[dannym-refactor] Location of Authorization Server Metadata about is-10 HOT 3 CLOSED

Hi Gareth,

1. The RAML is currently mistaken - the /.well-known/.. endpoint will hang off the the root path (e.g. https://{host}:{port}/.well-known/oauth-authorization-server.)
2. With regards to both versioning of the well-known endpoint (mentioned in issue #9) and multiple issuers on the same host, the thinking currently is that we define another text record in the DNS-SD announcement (call it issuer_path.), for a given auth server instance, that defines the {issuer} tag in the .well-known url. This will usually be blank or omitted, meaning clients default to the URL you have given above.
   If multiple auth services are hosted on the same host, or if integrating with an Off-the-Shelf auth server with a metadata URL with a different {issuer}, this issuer_path record can distinguish/point-at the auth server instances. From an NMOS perspective, this record could also give clients distinct server metadata URLs for different versions if we needed to - using two DNS-SD records with different text records. In this case, both the api_ver and issuer_path records may both be equal to v1.1 for example.

I hope that makes sense...

from is-10.

Thanks, that does start making sense. I think it's going to be simpler to document the /.well-known/ URL via separate means, whether that's pure documentation or a separate RAML file.

from is-10.

worked out

from is-10.