8 replies to this topic

[Xemdo]

I designed my own website and it has it's own database with usernames and passwords and other stuff in the database. Is it possible to make IP.Boards use the username and passwords from my website? And if so, is there any resources I can use to help me do this?

Thanks!

[Wolfie]

I designed my own website and it has it's own database with usernames and passwords and other stuff in the database. Is it possible to make IP.Boards use the username and passwords from my website? And if so, is there any resources I can use to help me do this?

You could use IP.Converge to do it, you would just need someone to create the necessary module to work with it. Once it's set up, your members could sign in using the same email/password to sign in and it would then populate the IP.Board structure.
IP.Converge: http://community.inv...739-ipconverge/

I should point out that IP.Converge is getting phased out as it won't be needed anymore. When IP.Board 3.4.0 is released, it's supposed to be flexible enough to more easily work with other databases.
Read more here: http://community.inv...te-ips-connect/

There's also more to learn about the future of IP.Board and the other apps.
First: http://community.inv...and-the-future/
Second: http://community.inv...e-changes-live/

I believe you will find all of that information useful.

[ZackL]

There are a number of resources available. For one, you're able to, as of 3.4, use "IPS Connect" to make an external database/system be the master accounts. 3.4 isn't currently out, so you'd have to wait for it to use this feature.

However, if you don't want to wait, you can utilize the 3.x Login Methods for IP.Board. I can't find a link for any articles I remember seeing around here that talked about implementing login methods, however. I do believe though you could sneak a peak at the source for some of the existing login methods.

[Manifield]

I have the same question, albeit in a different way.

So I have my own PHP website, how can I:

1. Use IPS user data in my PHP application. Is there any official docs specifically for this?
2. How to track IPS user login sessions in my own PHP website / application? So that when user logs in IPS, it is also logged in across my PHP website.

As you can imagine, this is pretty important stuff.

Thank you!

[Wolfie]

1. Use IPS user data in my PHP application. Is there any official docs specifically for this?
2. How to track IPS user login sessions in my own PHP website / application? So that when user logs in IPS, it is also logged in across my PHP website.

This page is like a starting point for developers:
http://community.inv...developers.html

This should cover what you're asking about:
http://community.inv...-logged-in-r328

[bfarber]

Check out the developer's starting point page Wolfie linked to. There are articles that show how to create custom login modules, SSO modules, and how to use our member APIs and verify if a user is logged in to IP.Board (for using IPB's registration system on your own website).

[Manifield]

Thanks Wolfie and farber. So when is the 3.4 coming out? I suppose it's much easier with IPS Connect than with IP.Converge right? I'm better to wait?

[Wolfie]

Thanks Wolfie and farber. So when is the 3.4 coming out? I suppose it's much easier with IPS Connect than with IP.Converge right? I'm better to wait?

The only answer you'll ever get for release dates of IPS software is "When It's Ready™" as IPS doesn't provide release dates. Any time that they even give an estimate for when they hope to have something ready, a lot of people get all bent out of shape claiming that they were promised it would be released on that day, ignoring the fact that no such promise was ever made.

Whether or not to wait really depends on your needs. If you need something by the end of the year, I recommend Converge. Then when 3.4 is released, wait until Connect has the bugs worked out of it before switching over to it. I'm sure there won't be many bugs with it, but there are bound to be a few and it's not a good idea to start 'fresh' with something that has kinks in it. Reason being that you're not only dealing with bugs in the new feature (Connect), but then any unforeseen issues with connecting to your existing database. It's different when you're already accustomed to using IP.Board and such, but not a good idea when you're new to it. (I hope you get what I'm saying because I may not have explained it quite right.)

[Petr1fied]

You can always approach it from another angle and lock down registration via IPB and create/login to IPB accounts from your current site. I've done this myself.