That’s probably not the right module. Be careful of the names. I think what you are looking for is not “OpenID” but “OpenID Connect”. Sometimes people use those terms interchangeably, but they are two different things. There is some similarity in intent, but a complete difference of implementation between OpenID And OpenID Connect. Check the FAQ by OpenID.net. There is an entry on this specific issue.
But let’s answer the general question - The way to know for certain what is in any module is to examine the code in the repo. I’m not sure how much of this you know, so I’ll just try to be complete.
You or someone on your team should have received some information about how to connect to the developer portal. Included in that information is a link to sign-in to the Pantheon dashboard. (https://pantheon.io) On the dashboard for your devportal there will be a git repo URL.
In a terminal window on your desktop, you can perform “git clone ” to get a complete copy of all the source code. (you can also do something similar with many GUI developer tools).
Within the cloned source code tree there will be several directories that contain the source for modules. Example:
./modules
./profiles/apigee/modules
./sites/all/modules
..and so on.
The precedence of these directories is established by Drupal.
One of those directories will contain a directory that defines the module that you found in the Administrative UI. From experience, I’m guessing it is ./modules/openid .
This is a default module in Drupal and is described here: https://www.drupal.org/documentation/modules/openid
If you want to do OpenID Connect, the thing in ./modules/openid is probably not what you want.
I have used this OpenID Connect module successfully: https://www.drupal.org/project/openid_connect
I suppose the next question is, “How to get a new module to be available in Drupal?”
Here’s the short story:
- get the source code for the module you want (eg, download from https://www.drupal.org/project/openid_connect )
- insert the source code for the module into your local directory ./sites/all/modules/contrib . As a rule, “contrib” is for modules available from the community. “Custom” is for modules that you have developed independently and will not be shared with community. If you create a module and share it on a github site and then use it in your portal, it should probably be in “contrib”.
- git commit; git push
- via the Drupal Admin UI, enable the module you just pushed (Config > Modules > (Search for named module) > click enable > SAVE )
- via the Drupal Admin UI, configure the module you just pushed. (Varies)
More information about the openid_connect module is here.
OK, here’s a quick screencast showing this actually working:
As I mentioned in that screencast, to get this to work the way I wanted, I needed to make modifications in the openid_connect module. A version of the module with the modifications I made can be found here. To use that modified version, just git clone that repo into your own ./sites/all/modules/contrib/openid_connect . Then “git push” into your devportal.
One thing I forgot to cover in the screencast above is enabling the OpenID Connect Login block. This is covered here: