[OpenID] openid in a non-distributed situation?

[Andrew Chilton]

Hi All,

On 19/07/07, Eddy Nigg (StartCom Ltd.) <eddy_nigg at startcom.org> wrote:
>
>  Simon Willison wrote:
>  On 7/18/07, Gábor Farkas <gabor at nekomancer.net> wrote:
>
>
>  i'm trying to implement a single-signon system for an intranet-solution,
> and had the idea that maybe openid would help there.
>
> i understand that it's not what openID is meant for, but i thought it
> maybe could work in this situation.
>
>  On the contrary, I think OpenID is ideally suited for this.

Funny thing is, I was thinking this exact same thing last night and I
just joined the list a few hours ago. Must mean I'm in the right place
:-)

>  Example:
>
>  User submits "user" and the script appends .intern.yourdomain.com (the
> domain of your IDP server) it will request authorization from the IDP
> server, whereas "user.myopenid.com" would result in a failure because
> user.myopenid.com.intern.yourdomain.com doesn't exist.

Yeah. My plan was that people would just use their normal login name
(which I can check with a regex or a LUT) and I'd prepend it like so
<user>.openid.myintranet.host

There are certainly a few applications we have internally which could
do with accepting an OpenID (bug tracking, wiki, etc).

Cheers,
Andy

-- 
contact: Andrew Chilton
website: http://kapiti.geek.nz/