Encrypting passwords

[Lixje]

Hello,

I developed a site for my forum and I would like to use the accounts of forums to connect to the site.
I wonder how are encrypt passwords? (md5+salt ?) 

[Humming]

IPS 4 passwords are hashed using the following function

crypt($password, '$2a$13$' . $salt);

$password is the user's plain-text password, and $salt is the user's unique salt string.

Edited September 24, 2015 by Humming

[Stake™]

Are you using a content management system like WordPress?

[Lixje]

No, I do not use any CMS. The website is fully developed by me.

[titcrunch]

same with ipb 3 you can use the api for send ipb login systeme in your site

[Lixje]

With IPB4 :')

[titcrunch]

yes with ipb 4 you can make same in admin => connexion you can activate api and use it outside the ips

[Lixje]

 

None of these options lets you use the database forum to my website: /
I would just like to use the accounts of the forum on my site through a connection with php. The only problem I have is the IPB password encryption ... I do not know what the password is encrypted. I just know that it uses the password to encrypt and salt ..

 

[titcrunch]

they don't work like that !

you need create a login in external (exemple : a worpdress blog with login or you personnal login systeme in a website in php) and after you link this external database in your ipb forum with the same name option in your capture.

 

french version :

tu as besoin d'avoir une base de donnée de connexion externe deja crée que tu ajoute dans ton forum ipb avec l'option qui porte le même nom

[Lixje]

Okay, but the accounts will be the site which will be accessible from the forum? And not the reverse?

[titcrunch]

when a user subscribe in your site the account is add in forum so the user have one account for 2 database and so 2 websites (site + forum)

[Lixje]

Okay, but for existing accounts on the forum?

[Nervodx]

PS Connect provides a simple solution for any application to to implement single sign-on (SSO) with other IPS Connect compatible applications.

In an IPS Connect network, there will be one "master" application and any number of "slave" applications.

The IPS Community Suite (versions 3.4 and above), can serve as either a master or a slave in an IPS Connect network.

This article will show you how to connect two IPS Community Suite installations using IPS Connect.

Before you set up, you will need to decide which installation will be the master, and which will be the slave.

Generally speaking, when setting up an IPS Connect network, the "new" installation (which does not have any existing user data) should be the slave. If you are connecting two installations which both have existing user data, it doesn't matter which is the master and which is the slave.


Important Information about Single Sign-On

In order for Single Sign-On to work properly, the slave application(s) need to read cookies set by the master application.

Since cookies cannot be read across domains, this means that your slave application needs to be on the same domain or a subdomain of the domain that the master application is on.

For example, your master application might be mysite.com, and the slave application might be something.mysite.com.
It will not work if the master application is on mysite.com and the slave application is on somethingelse.com.



Obtaining the URL and Key from the Master

Once you have decided which will be the master, you will need to obtain two pieces of information from it - the IPS Connect URL, and the IPS Connect Key.

This information can be obtained from Admin CP --> System --> Log In Management.




Setting up the slave

To set up your IPS Connect network, you simply need to input this information into the Admin CP on your slave installation.

To do this:

• Go to Admin CP --> System --> Log In Management on your slave application.
• You will see a module called "IPS Connect" - click the pencil icon to edit it, and toggle the "Log In Enabled" setting to "Yes".
• Now click the icon next to the pencil icon for "IPS Connect", which looks like a cog - copy and paste the IPS Connect URL and Key which you obtained from your master application and.

If your slave application already has member data, you want to make IPS Connect the primary log in module, and use "IPB Internal" as a fallback. To do this, simply drag and drop "IPS Connect" above "IPB Internal".



If your slave application does not already have member data, you can disable the "IPB Internal" method completely - this is the recommended set up if possible in your circumstances.
To do this, simply disable the "IPB Internal" method in the same way that you enabled the "IPS Connect" method.

That's for IPB 3, should be similar in 4.

[Lixje]

I d'ont use IPS connect, my website is not compatible ! 

[Lixje]

UP :/

[Lixje]

Thank's you very much Humming !