Re: [webfinger] Automated Service Configuration now uses webfinger

["Markus Lanthaler" <[e-mail]>]

On Tuesday, July 09, 2013 3:46 PM, Cyrus Daboo wrote:
> Hi Markus,
> 
> --On July 9, 2013 at 11:12:33 AM +0200 Markus Lanthaler wrote:
> 
> > I think doing the opposite to make it consistent might be better. The
> > service-configuration document doesn't contain any information depending
> > on the user. So, returning *and* requesting
> > https://example.com/service-config would be better in my opinion.
> 
> That is not true in general, and I will try and add an example to the spec
> to illustrate that. e.g., some users may be given access to a service that
> other users do not have (and should not see at all) - perhaps some
services
> are "for-pay" and the user hasn't signed up yet.

I wasn't generalizing but talking specifically about the examples in the
current draft.


> Another aspect we have not addressed is the possibility that the user id
> used to login to the advertised services may be different from the id
typed
> in to to discovery - so those id's ought to be in the service config
> document too.

True, but that should be a separate example. The best would be to describe
both mechanisms and, in the case the "id" query parameter is required, it
should be included directly in service-configuration URL in the WebFinger
response as Paul noted.


--
Markus Lanthaler
@markuslanthaler