Can I access the user's steamid?

Giovanni_Paul

Is there a way for me to see what a certain user's steamid is after they linked their steamaccount to my website? If I am able to get the steamid64 which gets sent as a response over openid I would be able to turn my website into a hub for all my gameservers where players can see all kinds of stats and achievements they've acuired on my servers on the website as well.

Your service already allowed me to make it possible to force my members to log in with their steam account, but it would be more awesome if I could actually make use of this information other than just the quick registration and spam prevention. If it's not possible, see it as a suggestion to make your product even better.

Fred_Pinel

Hi,
The short answer is yes :-)
However, it does require some additional work to get to.
We provide an API (web-based) that allows you to retrieve this information (and much more), but you would need to program that in (docs.oneall.com/api/resources/users/read-user-details/).
Another possibility, that you're suggesting, is for our plugin to do this work, and store this somewhere in Vanilla. You would still need to access it, use it, etc. This information is already going through your Vanilla application now, only not stored.

We're not sure what the best way to provide this would be. Maybe some hooks?
We can have look into this, but your suggestion, as a user, would be valuable to us!

Regards.

Fred_Pinel

Thanks for your comments.
No problem for storing the data (sorry for the confusion), I was wondering how you (or another Vanilla site owner) could then make use of the steamid data easily, such as in another plugin or so.
Anyway, we'll follow your suggestion, and see how to integrate this into Vanilla.
Thanks again.

Giovanni_Paul

I'm not a PHP programmer, so I wouldn't know how to implement this in vanilla with your API.

I think the best way to store this in vanilla would be a (seperate) table in the database with the information you supplied. I already noticed that you generate a record in the gdn_oasl_identity table where you link the identity (PK) with the user (FK). Perhaps it would be an idea to add a column called: provider_primary_identity where it stores the primary identifier for that particular provider, if any. In most cases this information will be publicly accessable. When it isn't you could always fill this field with null.

This way I can access the primary identifier for each service in my own database without making thousands, or in some other cases ten-thousands, of API calls per day.