Thread

Okay, now I found an actual bug, though it is only in the sample controller.

In the auth.php controller file, in function forgot_password():

$identity = $this->config->item('identity');

should be:

$identity = $this->config->item('identity','ion_auth');

I’m sure this has been asked but the search feature on the boards isn’t great. Can this be used on Codeigniter 2? Also, is this the most up to date one to use?

http://benedmunds.com/ion_auth/

As in, there’s no Ion_Auth v2?

I’m sure this has been asked but the search feature on the boards isn’t great. Can this be used on Codeigniter 2? Also, is this the most up to date one to use?

http://benedmunds.com/ion_auth/

As in, there’s no Ion_Auth v2?

Yes, you can use IONAuth in CI v2.x
And latest version is posted here: http://github.com/benedmunds/CodeIgniter-Ion-Auth

Although there are not newer versions posted recently (AFAIK)

Shauna,

The username functionality is for people that want to use usernames as the identity and they will need to be unique.  If you are using email it doesn’t matter all that much what you pass as the username unless you are wanting to use it for something else.  If you use the email as the username and the identity is email it should always be unique so this code won’t matter.

Shauna/Gbar,
On the issue with the example controller, thank you!  This has been fixed with commit ebf74dda1c18d24f3904f918e6b17be586a0181c.

Citizen,

It is compatible with CI2.

Ion Auth v2 is available but it is still alpha, it is located here if you want to try it out: https://github.com/benedmunds/CodeIgniter-Ion-Auth/tree/2

Citizen,

It is compatible with CI2.

Ion Auth v2 is available but it is still alpha, it is located here if you want to try it out: https://github.com/benedmunds/CodeIgniter-Ion-Auth/tree/2

Is v2 usable? I’m starting a new project and I’d like to use v2 if it means updating in the future is just an upload/overwrite instead of having to change all my code.

Citizen,

v2 is usable, the basics are there and won’t change much but there are most likely a few bugs.

Cool, I’ll test and provide the best feedback I can 😊

Config question: should I store the salt in the database? What are the pros and cons? Which is more secure?

Edit: more questions:

As part of the install, do I need to run the .sql file to add the tables via phpmyadmin or is there a page to handle this?

And if I config CI to use smtp mail, will the emails sent by ION use SMTP automatically or is there custom email code?

One small suggestion: you might to include the adding of ion tables as part of the installation portion of the user guide. The problem with just running ion_auth.sql through phpmyadmin is that it doesn’t add your CI table prefix.

Citizen,

Storing the salts separately in the database is not any more secure, it just helps if you need to integrate with any other auth systems or if your porting an existing system to Ion Auth.

Ion Auth v1 has custom config settings that will need to be updated.  Ion Auth v2 will inherit the settings from your email config file.

Thanks for the feedback!

For my application to function the way I wish I require user preferences; What do you think the best approach to this would be? Add the preferences inside the meta table? or create a table that functions like the meta table for preferences? I’m leaning towards the latter.

The only issue? I’m not sure how to incorporate the preferences table without breaking Ion Auth; I realize work on Ion Auth 2 is underway and as you’ve mentioned it will be extendable. This is a feature that I’m trying to incorporate “immediately”, but will also help develop for Ion Auth 2 if you need help, suggestions, or testers..

And now that I’ve rambled on for far too long, I guess my question really is how would I add a second table identical to the user’s meta table to hold nothing, but preferences? Do I just add those functions to the library after adding the necessary Database Schema?

And and All help is appreciated!

Austin.

I’d recommend putting that in the meta table; that’s a perfect use case for the meta table.

One small suggestion: you might to include the adding of ion tables as part of the installation portion of the user guide. The problem with just running ion_auth.sql through phpmyadmin is that it doesn’t add your CI table prefix.

Since Ben is so busy, I decided to make a few quick edits to the pre-existing sql to include prefixes and I’ll attempt to make a few edits to the library to let it utilize prefixes using a configuration key.

Thanks Austin!