Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 6 of 6
  1. #1
    Regular Coder
    Join Date
    Apr 2006
    Posts
    154
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Question Login in a diferent site

    I have a site of an university in PHP and a joomla site for university administration. Can I have a authentication form in the main site for logon the joomla site?? If yes how can I do that??...I have tried several times without success!!!

    I have a the next form:

    Code:

    Code:
    <form ID="secLogin" action="secretaria/index.php?option=com_comprofiler&task=login" target="_blank" method="post">
        
    			<p>Nome:
    			  &nbsp;<input name="username" id="username" type="text" size="20">
    			  <br>
    		Senha:
    		<input name="passwd" id="password" size="20" type="password">
    		</p>
    		<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<input name="Reset" type="reset" value="Limpar">&nbsp;&nbsp;<input type="submit" value="Submeter" /></div>
    			
      	 </form>

    And result say that I haven“t permissions!!! Which permissions??

  • #2
    Senior Coder
    Join Date
    Jan 2007
    Posts
    1,648
    Thanks
    1
    Thanked 58 Times in 54 Posts
    It depends on how the login system in Joomla works, and on your own site.

    Cross-over logins are not that easy.

    It usually requires modification on both sides.

    This isn't really a must have, but more like a nice to have. Unless you want to do some research it might not be worth the effort.

  • #3
    Super Moderator JohnDubya's Avatar
    Join Date
    Nov 2006
    Location
    Missouri
    Posts
    634
    Thanks
    12
    Thanked 18 Times in 18 Posts
    It definitely would be a pain. I haven't tried it before, but I've heard of people doing it. Do a search on here and Google to see how other people have accomplished this. I know it would definitely take either modifications of the tables, or you would have to somehow join the different columns together. It would be complicated, but most likely possible.

  • #4
    Regular Coder
    Join Date
    Apr 2006
    Posts
    154
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Do you have examples of people or post's of that??

  • #5
    Super Moderator JohnDubya's Avatar
    Join Date
    Nov 2006
    Location
    Missouri
    Posts
    634
    Thanks
    12
    Thanked 18 Times in 18 Posts
    Not without searching, which you all can do too. I only say what I said above because I researched into how to join two user database tables because I was thinking of linking two Joomla sites together. From what I read at that time, and from what I know now as a PHP/MySQL Programmer, you would have to have two different connections to two databases. Then, you have to check the entered username/password from both tables, choose which table to use the user information from, etc. I guess if you wanted to keep it more on the simple side, you might be able to do it without too many problems. I'm sure there are others who have actual practical experience in this, so I'll let them give concrete details.

  • #6
    Regular Coder meth's Avatar
    Join Date
    Jan 2003
    Posts
    262
    Thanks
    0
    Thanked 9 Times in 9 Posts
    Recently did this for a cross domain auth between asp.net/mssql and 2 load balanced php/mysql servers. The amount of work involved is not small. I'd advise against it unless cross domain logins are essential to functionality.

    Gist of it went like this:

    PHP1 managed session data in mysql for both PHP1 and PHP2 servers.

    PHP1 had the detailed user table with a column php_session_ID which was updated with session_ID() from the custom session handlers and auth scripts.

    ASP1 server mirrored only essential user records in mssql (userName, Password, Access_ID), with a column asp_session_ID. ASP1 User records managed from PHP1 except for asp_session_id, ASP1 took care of it's own session handling.

    PHP and ASP configured to session.use_only_cookies.

    Auth scripts on all servers checked for session_id cookies from opposing platform. If set, queried the opposing database for user.xxx_session_id. If still current, user auto-logged on.

    Both platforms had great session handlers for garbage collection to keep user.xxx_session_id current.

    The only problem we encountered were from firefox and ie users with 'maintain session state' mods active. They could logon, but logging off x-domain was a migrane to tackle.

    Bottom line - I wouldn't bother. Let your users logon twice.
    I do Web Design, Brisbane based.
    More time spent in PHP/MySQL Web Development.
    And Search Engine Optimisation takes up the rest of it.


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •