• Plugin Contributor martinkilkie

    (@martinkilkie)


    Hi Colin, I expect you are a busy person and I noticed that you updated the plugin recently, so thanks for all the effort. I expect the plugin to be of great value to my family as they are always getting confused between the two logins.

    My problem may well be very basic but I have I think successfully installed the SSO for my site Kilkie.org and want it to SSO to the TNG site kilkie.org/tng. There is a little bit of a conflict between PIEREGISTER re .htaccess but that I am sorting.

    The key symptom is that when I log into the WP site KILKIE.org and then switch via a WP menu item to Kilkie.org.uk I find I am not logged in. For my test user I used a hand generated userid and password which are the same on both sites. Perversely if I use a test user that has no equivalent on TNG it creates that user and password as guest (as expected) but still does not log me in to TNG.

    Many thanks and grateful for any help due to my failing to understand.

    here are my settings in the plugin;

    tng installation location: /homepages/16/d387908500/htdocs/KFHSWP/tng

    tng installation URL: https://www.kilkie.org/tng/

    • This topic was modified 11 months, 3 weeks ago by martinkilkie.
    • This topic was modified 11 months, 3 weeks ago by martinkilkie.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Colin Stearman

    (@britcoder)

    Hi Martin,

    Sorry to hear that the SSO plugin may not working for you. Reading your description of what is happening, it seems that, if you create a user in WordPress, the user also gets created in TNG but when you log into WordPress using that user and the go to TNG you are not logged in. I’m assuming that’s right.

    An important point, when you’ve created the user in WordPress and want to give them more than guest access to TNG, make sure you are going into TNG’s Administration Panel, and the User’s area and enabling the TNG account in the Review tab for the person. The plugin won’t log the user into TNG automatically until you approve the account there (which you don’t have to do to give them guest access!). The FAQ section of the plugin says this:

    Approving the WordPress registration does NOT approve the TNG one. That must be done separately in TNG’s administrator panel, so that you can decide whether or not to give them TNG access, and if so, at what level, branch, etc. 

    Assuming you have done the above, here are my questions:

    1. What version of WordPress are you running?
    2. You have installed 1.1.2 of the plugin I assume.
    3. Did you install an earlier version and have it work?
    4. What version of TNG are you running?
    5. I am assuming from your details that WordPress and TNG are on the same server?
    6. Can you give me a basic user test account so I can see first-hand what is going on?
    7. When you entered /homepages/16/d387908500/htdocs/KFHSWP/tng into the settings in the TNG Installation Location box did it accept it and leave it in the box, or complain that it couldn’t find the TNG installation, and empty the box? My guess is the former.

    Once we’ve got these preliminaries out of the way I can look into, and describe to you, how the auto sign-in to TNG so we can figure out what’s going on.

    I hope this helps. Please le me know either way.
    Colin

    Plugin Contributor martinkilkie

    (@martinkilkie)

    Thanks for the quick reply Colin.

    The suggestion that I create a guest account is good one. I will send details to your contact page on your family website. I will make the same account on both wordpress (kilkie.org) and tng (kilkie.org/tng). I am not sure how much good that will be unless I let you see the inside. Happy to do that too via some non-public way of getting account details to you.

    I suspect that some of the problems are to do with pie-register. I use this to have most of my wordpress site only visible to logged in users. I dont really use any other of the pie-register features and was very disappointed that there is no native restriction feature in wordpress akin to K2 in Joomla, but heyho!

    The other symptoms that I have with the sso are changes to redirection and .htaccess. Eventually I want the TNG website only to run from logged in links on my wordpress account. A significant number of my family (all of them in fact) have problems remembering the two different urls even though it is a top link on both sites. So I will be enormously grateful if we can get the link working.

    I can see that sso adds a whole chunk of redirections to my .htaccess which causes some of the redirection issues, something about double encoding the urls (suspect this is pieregister conflict). When i enable sso the wordpress login works ok but not the tng login.

    Important first step i think is deactivating pie-register for a time which makes all of the menu and posts show publicly but might get us to resolving the sso issue.

    My working folder is jammed with different versions of .htaccess (in the root and those from /tng subfolder).

    to your questions:

    the tng installation location was entered as https://kilkie.org and then your plugin changed it to the whole hoster (IONOS) link – /homepages/16/d387908500/htdocs/KFHSWP/tng

    I am running 6.8.1 WordPress.

    I did install the previous version of sso which gave the same symptoms. It auto-updated to 1.2

    tng is version 15.02 with slightly customised template13.

    Not sure if this is clear enough but Im grateful for your time.

    Martin

    Plugin Contributor martinkilkie

    (@martinkilkie)

    At the moment i’ve left the site as was (with pieregister activated and sso deactivated). One problem i have is that when sso is deactivated it doesnt delete the entries from /tng/.htaccess. text or whatsapp me to get changes to the above. Some combinations get locked me out of both sites and i need to rename plugins and change .htaccess to get back in.

    • This reply was modified 11 months, 3 weeks ago by martinkilkie.
Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘failed sso’ is closed to new replies.