OpenID

As you can see from the "External Identities Initiative" issues tag, OpenID has apparently been removed from the core for Drupal 8 while OAuth is being added. However, the exact status is not clear to me because of the spaghetti-web of related issues, comments, modules, etc. at Drupal.org.

I've been reading, and still looking for clarity.

Looks like support for OpenID is better in D6, as compared to D7.

I'd like a Drupal 7 solution:

X number of Drupal 7 sites.

Register at any of the associated sites, will create a user on that site, and also sync that user to the OpenID server (Drupal?).

Login to a different associated site, you are authenticated via the OpenID server, a local drupal account is created.

Changing something like email address, Last name , etc would be sync'd back to the OpenID server.

Hi, I have a Google Apps for business account (our own domain not @gmail) that I'd like to use OpenID for, so users do not have to create a new account at the website, but rather, a user can login with their Google Apps username/password. I have read a lot on the subject, but I am still not sure how to implement it in Drupal 6. I tried typing 'https://www.google.com/accounts/o8/site-xrds?hd=<example.com>' but after redirecting to the google apps login, I get "OpenID login failed" on the Drupal site. Can someone please advise? Thank you!

I am using Drupal 6.25

It seems as though OpenID is at a tipping point in the Drupal community. While we have a lot of related modules, many seem to have gone into a dormant phase and aren't being actively maintained. At the same time, there's a resurgence of interest in OpenID from users of Drupal and a desire for robust implementations, particularly in the US federal government.

We're working to support several IdP's as a relying party. Some of the IdP's we want to collect data from use sreg for data exchange and some use each flavor of AX (axschema.org and schemas.openid.net). Does anyone have guidance on how to determine the format that a given provider uses, preferably programmatically, so that we're not filling the request with key=values which will not be acknowledged?

On the subject of AX, is axschema.org dead? From what I understand it's the most common AX schema used but it appears the site is gone from the internet.

Yesterday was released Drupal 7.9 which includes 3 critical fixes for Openid plus one normal fix.

• #575810: OpenID discovery spec violation - follow redirects.
• #1076366: OpenID discovery spec violation - fragments are removed from claimed id
• #1120290: Provide transition for accounts with incompletely stored OpenIDs
• #160163: Login with OpenID link has mis-encoding of #

I'm currently using the OpenID Single Sign On with provider and client and with modules for syncing user profiles. Here's a patch I submitted to sync user profile pictures: http://drupal.org/node/1196160#comment-5003986. I think overall this solution works quite well, though could still use some work.

What sort of issues are people having / working on?

A couple issues I'm working on:

Syncing User Membership across sites
1.) how to sync both the creation and updating of group nodes (since my sites are using modified Atrium sites) between the hub and subsites and

Hey there, I'm wojtha, fresh co-maintainer for the OpenID module.

Now I'm trying to fix the critical bugs of the OpenID in the D6 and D7. But I'm not an expert in this area, I dove to the OpenID standard 5 months ago for the first time so any help will be appreciated. Now I'm focused on my personal issues with the OpenID, trying to get following three and several connected issues to the next Drupal 7.x release:

Hello,

I'm just trying to get all information, spread out in different nodes and comments, together into one single post:

We implemented a OpenID single sign on solution for some of our clients (we call it Omniauth). It's based on Development Seeds great work on an OpenID Single Sign on solution for Drupal. Besides general improvement, instead of using feeds, foaf and PubSubHubbub to synchronize user information we used OpenID's own update_url (http://openid.net/specs/openid-attribute-exchange-1_0.html#fetch_request) and store_request (http://openid.net/specs/openid-attribute-exchange-1_0.html#store_request) to share user information between sites.

Omniauth includes the modules that are necessary, exported configuration into Features and installation profiles for both provider and relying parties.

I made a screencast to allow you to understand easier how to set up Omniauth and it's provided functionality at this moment: http://vimeo.com/xamanu/omniauth-drupal-openid-single-sign-on-solution

the single-signon options for mere-Drupal-mortals seem to be pretty thin, which is rather suprizing considering the flagship Drupal Gardens uses OpenID

I am looking at setting-up a network of sites within Aegir hosting and I've been spending a lot of time spinning my wheels with Bakery and OpenID type "solutions" - I've been annoying people and arguing and basically struggling through up the learning curve

This is some basic information I've gathered about support for Google Apps OpenID provider in Drupal. I'm not an expert on this, but since I found virtually no clear information I'm going to dump what I found here.

Hello,

I'm wondering if the following use case scenario example is possible.

I want to have an Drupal website relating to ART, for example.

I want to allow a single sign-on for my users (probably utilizing something like OpenID).

I want to allow a single user to have a profile (or identity) as an artist because he paints art.
I also want to allow that same user to have a second profile (or identity) as an art dealer, because he runs an art shop.

Hi all,

there's one thing about this OpenID feature. I've been searching to find the answer for this question, but I didn't succeeded. The main idea is to use single login and password for variety of sites. So far so good. Correct me if I'm wrong, but if you're asking for new account, you have to provide some non-OpenID password in order to log in for the first time and only after that you're able to define your OpenID identity.

Would it be possible to skip defining non-OpenID password and to use OpenID identity straight at registering as a new user?

dalibor

Hello !

My name is Jan and I'am member of Scout Associations of Polish Republic.
Half year ago we are tackle with authorization problem. We had many scattered applications, without any global authorization system. We start considering OpenID (this was the first think) but more important things was on one's plate.
One of this most important things is implementing Drupal (what is almost done). Incidentally this is good time to back to talk about OpenID.

With Drupal core OpenID module, users can authenticate on your Drupal
site with
OpenID. With the OpenID extensions AX and SReg it is also possible to
exchange
with user profile data. Alex Barth, Darren Ferguson and I have worked
in the
past months together to improve the existing OpenID AX / SREG modules:

This is a working document as a follow up to RFC: OpenID roadmap. It summarizes the current tasks being worked on for accomplishing steps 1 and 2 outlined in the roadmap.

Step 1

OpenID Provider modules

• (削除) #399746 Refactor dependencies AX - Persona OpenID Provider AX / OpenID Provider Persona (削除ここまで)
• (削除) #430332 Make SREG independent of Persona OpenID Provider SREG (削除ここまで)

Based on an email conversation I had with Darren, Evgeny, Aron Novak and Walkah I pulled together this roadmap for advanced OpenID features (attribute exchange, provider, etc).

The goal is to reduce the overall number of modules involved in deploying OpenID attribute exchange features, to expand on existing content profile integration, to remove dependencies on modules that are not used in all use cases and to push changes into OpenID and OpenID Provider where it makes sense.

Is there a way to restrict user registration to openID only. I was not able to find such a module, though I looked at a few openID related modules. Optionally it could also require openID to log in such as the LDAP module does already (and disable the regular login mechanism except for uid 1).

UPDATE: We are in room 142 and in #drupal-openid (on freenode) if you want to join in.

Let's focus some development energy on OpenID - related technology!

There are lots of things to do:

• Simpletests for OpenID module in D7
• Move toward a stable OpenID Provider release
• Work with OAuth
• Core OpenID issues
• User experience issues

Hope to see you there!

I would like feedback and recommendations on researching how Drupal generates unique keys for a new Drupal installation and how OpenID utilizes the keys when validating a new user Session for a valid user account.

Subjects Involved
1) Building a multi-site deployment system that will create new Drupal multi-sites using database replication.
2) Each site requires integration with an OpenID server and authentication of local users accounts to OpenID.

Research
1) Conflict Resolution.