Redmine

If the sreg response doesn't contain a unique login, first/last names, and an email address, this patch will still respond with the registration page.

I think the correct way to approach OpenID-only operation is to make first/last name and email optional, and allow changing the login name (since it's not used for logging in any more). I want to use OpenID in the first place to allow identity with as little effort as possible, and requiring these fields erects a wall with little benefit.

Isn't the login the OpenID? In which case it'll be unique.

It's true that the email address must also be unique. It does fail over to the registration page, at which point an administrator must end up approving the request. This isn't necessarily a bad thing, since the clashing emails might indicate a problem.

However, I agree with what you said in the sense that making email optional would be nice. If you have OpenID you don't really need to have email be a primary key; you can use the OpenID instead.

Nope; the login is set to be the sreg "nickname". If your provider doesn't send back any sreg at all, you'll get the registration page with a confounding error about requiring a login name (and then you'll need to enter a password, etc).

I don't think it's possible to use the identity URL for the login, anyway; login names are restricted to letters, numbers, and a handful of punctuation.

There's a patch on issue #3780 that gets OpenID support closer to how it should be, by filling in dummy values when the sreg is missing something.

Alex Munroe wrote:

I don't think it's possible to use the identity URL for the login, anyway; login names are restricted to letters, numbers, and a handful of punctuation.

Seems like a fixable problem.