How do you authenticate your users?
- This topic has 2 replies, 2 voices, and was last updated 9 years, 6 months ago by .
Viewing 2 reply threads
Viewing 2 reply threads
- You must be logged in to reply to this topic.
Home › Forums › GovIntranetters › How do you authenticate your users?
Tagged: active directory, auth, ldap
Hi all,
I’m just wondering how you authenticate your users? do you sync with Active Directory or some other LDAP server, or just use the wordpress user manager?
Ive been looking at OneLogin it works great in terms of logging in the user but it requires further manual admin in the wordpress dashboard so specify Forum Roles and Line Manager etc.
Thanks in advanced
Hi Will
We’ve been using the GLogin plugin in conjunction with the One Intranet plugin to control access for some of our clients who use Google Apps. http://wp-glogin.com/ This allows staff to login from anywhere. We’re looking at Active Directory options for another client but I don’t have any advice on this as yet.
Otherwise, we control access via IP address lockdown which requires no login to view the intranet, apart from VPN access from remote locations where required.
Luke
Thanks Luke,
I’ll give the GLogin a try.
The profile link thats displayed when you visit your own Contact Card on the Staff Directory, is there a link that can be put into a custom menu item? so rather than them having to go through a long way to get to their profile, just add something to the menu?
I can’t find the code in the templates anywhere.
Cookie | Duration | Description |
---|---|---|
comment_author_email_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_url_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wordpress_logged_in_[hash] | Indicates when you’re logged in, and who you are, for most interface use. | |
wp-settings-{time}-[UID] | This is used to customize your view of admin interface, and possibly also the main site interface. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. |
_gid | 24 hours | Used to distinguish users. |