[nodebb-plugin-sso-steam] Steam/OpenID register/login

shinyidol

@a_5mith Thanks

Jurjee

Any updates on this? I really want to use NodeDB but this makes it pretty much useless for me. :l

julian

@Jurjee Hey, I have time to kill, I'll take a look.

Edit: Ready.

Jurjee

Wow, that was fast! Thank you very much!

shinyidol

@julian tried updating to this and causing my nodebb instance to stop. ideas?

a_5mith

@shinyidol the pull request Julian submitted hasn't been committed yet, so it's technically not fixed yet. You've got two options, you can either wait until the plugin developer accepts the changes, or you can fork the plugin and make the changes manually to your forked version. I'm not sure if there's an unwritten rule when it comes to taking over inactive plugins. As the old plugin would still exist.

shinyidol

@a_5mith yeah. i did a fork and manually updated and it didn't work

Jurjee

I haven't tried it myself but will check it out later today to see if it does work for me.

julian

Only the first one (#6) is required, #7 is just a renaming of the module for cosmetic purposes.

You can try to install my fork by running the following:

$ npm install git+https://github.com/julianlam/nodebb-plugin-openid-steam.git

If at a late date you want to uninstall it: npm unl nodebb-plugin-openid-steam, or just remove it from the ACP.

shinyidol

@julian appreciate the help, but not working. Running 0.43. Removed all previous versions. Then ran the npm command above. Clicking on Steam still takes to 404 error.

julian

@shinyidol Just want to confirm it is installed: npm ls nodebb-plugin-openid-steam?

shinyidol

@julian i think so.

root@blog:~/nodebb# npm ls nodebb-plugin-openid-steam
[email protected] /root/nodebb
[email protected] extraneous (git+https://github.com/julianlam/nodebb-plugin-openid-steam.git#3c81e2c58720bd111d1949cadda1e602834616dc)
npm ERR! extraneous: [email protected] /root/nodebb/node_modules/nodebb-plugin-openid-steam
npm ERR! not ok code 0

julian

@shinyidol Ugh, sorry about that, silly mistake. Please re-install.

When you re-install and run npm ls on that package again, the git hash should be: ca32b1a6e87b0682572c2cbf4400a17e42e1f4a4

shinyidol

@julian Well that got the 404 resolved. i was able to add my steam key and save it. but no additional login option becomes available.

julian

@shinyidol Once you save the steam key, a restart is required to load the new values into NodeBB

Radon

@julian Thanks for the tips on installing the git version. Now the admin panel options work

@nanoVapor Is there a way to link existing accounts, eg Admins, to their steam account without having to reregister etc. It would be nice for existing users to link to their steam account, then use either their previously registered acc or their steam account for Auth/login. Sorry if this is already answered, and thanks for the Steam auth plugin, great job!

julian

@Radon If your steam email matches the email you used to previously register on NodeBB, then the accounts should automatically merge...

Radon

@julian said:

@Radon If your steam email matches the email you used to previously register on NodeBB, then the accounts should automatically merge...

I thought the steam api couldn't give you e-mail information as the API is public. I don't see any e-mail checking in the source for the plugin either. Not to mention the fact that my steam e-mail and my user e-mail are identical anyway ( Even if my node bb account e-mail wasn't confirmed at the time ).

julian

Mm... in that case, then it would be impossible at this point in time to detect the account association. At a later date, we may add in the ability to do so via the user profile page, though that is not currently a priority.

Radon

@julian Friend of mine managed to associate the steamID with his existing account by using redis-cli. I believe that all the editing could be done by the plugin author, it just needs to be involved a little more during the registration process and possibly add some items to the profile page to allow association. I don't think this is truly a NodeBB issue. Thanks for the reply though.