Integration with Wordpress authentication

Asked

Viewed 1,218 times

2

Taking into account a site based on Wordpress and a management system that runs in the same domain, but with totally independent authentication features, I think to integrate the authentication of Wordpress with the management system, ie when logging in by Wordpress, I will automatically access the management system through a link in the Wordpress menu itself.

My need is to have user data available in the management system, such as id, name, surname among others.

If a user tries to access some restricted internal management system page without authenticating, the system should redirect him to Wordpress authentication.

I would like ideas for this integration and ideas for technical implementation.

php wordpress authentication integration

  • Have you thought about authentication per service (Google, Facebook, Yahoo, Openid...)? It is practical because it would be enough for you to consume the respective Apis and secure as much as the developers of these solutions can provide.

2 answers

4

I refer to my experience in a solution I worked on. In my specific case the authentication system was independent of Wordpress and the management system. In Wordpress a plugin built for this purpose authenticates the user in the authentication system and in the management system the same.

After successful authentication some of the user fields were updated in Wordpress as it is necessary for some plugins that can install that will require some of this user information not to mention Wordpress itself.

The separate authentication system has many advantages because it separates services and places expertise in each of the services. It can also centralize credentials in addition to many other advantages.

With the use of WebServices and the management of TOKENS for example, it was possible manage user actions in such a way that users only authenticate once, despite using the various services available.

  • Perfect. You can’t talk about system integration without at least starting by quoting Webservices :)

  • Excellent your conceptual solution. In fact, it would be even ideal to work with webservices, but I believe it would not be interesting in my case because of the cost x benefit, at least for the project in question. Now, technically speaking, the answer below @brasofilo meets the need quickly... but through the answers and comments, I’m inclined to leave authentication independent even as you mentioned.

  • 1

    @Danielaccorsi true it is more expensive to keep a separate authentication service, but what I realize today is that authentication should even be separated... speaking clearly for companies, because the growth in users can be exponential which in the future can pose problems.

  • @chambelix, funny as there were two practical solutions here. We have rich information on this topic. Each case meeting a specific need for complexity. That’s quite what you said now, and another: in my case WP would be for content management, and the system would be for company management, better let separate even, ie, are distinct users.

4


  • Thank you for the idea, it actually kills the problem. I will study this method. Taking into account the cost x benefit, I believe it is the most practical way. Thank you.

Browser other questions tagged php wordpress authentication integration

You are not signed in. Login or sign up in order to post.