Hi – I am trying to enable SSO across portals on a domain, but have not been successful.  Specifically, I want to set the parent site (www.mydomain.com) as the master, with each child portal (e.g., www.mydomain.com/child1) eligible for SSO.  In other words, every authenticated user on www.mydomain.com would be authenticated on each child portal. 

Can you please advise what I am doing wrong? 

Details follow:

• DL: 03.30.00
• DNN: 04.09.04
• Configuration:
  
  DL configuration on login tab for parent portal:
  Enable Single Sign On:  TRUE
  Master Portal:  child1
  Add user to portal… TRUE
  Syne User Roles… TRUE
  
  DL configuration on login tab for child portal:
  Enable Single Sign On:  TRUE
  Master Portal:  parent
  Add user to portal… TRUE
  Syne User Roles… TRUE
  
  Security roles:  Same on parent and child
  
  
• I have a test user on the parent portal that can login.  But when I attempt to login to the child portal using this user account, the login fails with the default message (Login Failed, remember that Passwords are case sensitive).
•  I was expecting the user to be authenticated and eligible for login on the child.

 

Please advise what I am doing wrong.

Thanks in advance.

Try changing the parent portal, Master Portal from child1 to parent.

Hi - I have made this change.  I am still unable to login on the slave portal, and when trying to login on the master, it throws the following error:A critical error has occurred.
Invalid column name 'CreatedByUserID'. Invalid column name 'CreatedOnDate'. Invalid column name 'LastModifiedByUserID'. Invalid column name 'LastModifiedOnDate'.
I can login to the master successfuly when disabling the SSO option.
Please advise.
Thank youl.

Mark,

I'm currently using DNN 5.4.4 when I checked the users table I noticed that CreatedByUserID, CreatedOnDate, LastModifiedByUserID and LastModifiedOnDate are fields listed last on the table.  I would normally included these fields first; therefore I suspect these were added during a DNN update.

I would check your users table structure.  If these fields are missing consider upgrading your DNN installation or adding these fields manually.

CreatedByUserID           int   allow nulls
CreatedOnDate              datetime allow nulls
LastModifiedByUserID     int  allow nulls
LastModifiedOnDate        datetime allow nulls

I'm not sure what version of DNN started using these fields, something you would have to ask DNN Users support group or Data Springs.

Kris

Hi Mark / Kris...

Kris - Thanks very much for your community help and assistance!

Mark - I see the problem here... Although our modules are built and support earlier versions of DNN (all the way back to 4.6.x) it looks like when Dynamic Login 3.3 was released we added a new feature that was not really code driven but rather data driven and our developer was testing and building the query against 5.x. So... First, this should only be getting executed whenever you enable "Syne User Roles" and to be honest I don't really think you need that feature enabled. We added this feature as it was a customer paid enhancement and really didn't see a reason to include it into the release but basically what it does is allows the master portal to always be the 'HUB' for the users security roles.

So, if this feature wasn't enabled what would happen is that the user would be added to the portal and the same security roles they had on the main portal would be added to them as a child portal (role by name) EXCEPT for the role called 'Administrators'. If they had a role on the parent portal called 'California' it would also add that same role (if it existed on the child). For the most part the majority of customers were able to use this because their roles didn't change to much.

You really only need that feature enabled if you wanted the 'sync' to happen for each and every user, every time they signed in. The difference is that the feature when disabled will only sync the roles for the first login instead of each and every time.

If needed we can review adding / changing the query to support 4.9.x or if it still won't work we can provide you with a refund as long as you purchased the standard edition only.

Thanks,

Chad

Chad and everyone else who responsded to this thread -
Thank you, and I'm up and running by un-checking the sync field.
BTW, this experience is an excellent example of how this type of support should work -- good input from the community with the declarative response (and explanation) by the vendor.
Excellent work everyone!
Mark