Go Back   vb.org Archive > vBulletin 4 Discussion > vB4 General Discussions
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 03-26-2014, 03:04 PM
italynstylion italynstylion is offline
 
Join Date: Apr 2010
Posts: 22
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default User Access Lifecycle Management: Access based on employment?

Weird thread title I know....sorry for being vague

Basically, what I'm trying to do is make a vBulletin site where employees from two companies have access to register for the forum. Essentially, the forum will have somewhat confidential information inside of it and I want to limit access based on current employment by either of the two companies. This way, in the event someone leaves the company or gets fired they will no longer have access to the forum. I'll have access to two different employee databases (one per company) and I'm envisioning some sort of vBulletin utility that checks these databases for a user. If they exist then they get in.

Any tips or ideas for how to do this?
Reply With Quote
  #2  
Old 03-26-2014, 10:28 PM
Elixar's Avatar
Elixar Elixar is offline
 
Join Date: Jan 2014
Posts: 579
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

I would say that you would need a modification created for this. Try posting a request here.
Reply With Quote
  #3  
Old 04-03-2014, 05:06 PM
italynstylion italynstylion is offline
 
Join Date: Apr 2010
Posts: 22
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

I've crafted a solution for this (described below) that seems to work quite well. More testing is needed but preliminary testing yields the desired results.

Here's how you you set it up.

(Step 1)
Setup your forum so that only registered users can view it.

(Step 2)
Configure "user registration options" such that new users who register will receive an email with a registration confirmation link that they MUST click to activate their account. This ensures that bogus emails can't be used.

(Step 3)
ForumsMods designed a vbulletin mod that allows only certain email address domains to be used for registration. For example, @GMAIL.com would allow all Gmail addresses to be used. But if I didn't explicitly state @HOTMAIL.com then all users trying to use a hotmail account (or anything else) would be denied registration. I've personally installed this mod on VB 4.2.2 and it works like a charm! So the first step to achieving role based access (based on employment status) would be to use this mod to define email domains for your company or companies. This assumes that your company already has a means for deactivating past employee email accounts.
(mod link)--> https://vborg.vbsupport.ru/showthread.php?t=188418

(Step 4)
Dragonbyte Tech has blessed us all with a great security mod for vbulletin that increases security in many different ways. The features list is quite long but the main feature we are interested in is the "universal password reset" function. This allows an administrator to reset everyone's password except yours (the admin). This feature is actually available in the Lite version. Install the mod so you can gain this very important feature.
(mod link)--> http://www.dragonbyte-tech.com/product/123-vbsecurity/?

(Step 5)
Now that you have the VB Security mod installed go to your admin panel under Dragonbyte VB Security and change the options for "Security Watchers: User Data". This configuration gives you the ability to have the mod log changes to user profile fields and perform certain actions should a criteria be met.
Setup a rule that states if a user changes their email address the forum will automatically send the admin an email and the user will be banned. Since email addresses don't change while an employee is employed this will alert you to someone trying to retain access following employment termination.

(Step 6)
Set a calendar reminder to reset all passwords after a specified time. I'm choosing every 90 days as that will likely be sufficient for my needs. When the password is reset all users will get an email stating their password was reset. This email will include their user name and a temporary, randomly generated password. The email even includes a direct link for them to reset the password. I'm choosing to let my users use their old password so I don't piss them off
What's important here is that if the user no longer has access to the email address associated with their account they will NOT be able to reset their password and therefore will not have access to the forum.



And that's it! Now you have a way of ensuring your entire forum is locked down to ONLY users who have company email access. Enjoy!
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 01:55 AM.


Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.03366 seconds
  • Memory Usage 2,179KB
  • Queries Executed 11 (?)
More Information
Template Usage:
  • (1)SHOWTHREAD
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)ad_showthread_beforeqr
  • (1)ad_showthread_firstpost
  • (1)ad_showthread_firstpost_sig
  • (1)ad_showthread_firstpost_start
  • (1)footer
  • (1)forumjump
  • (1)forumrules
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (1)navbar
  • (3)navbar_link
  • (120)option
  • (3)post_thanks_box
  • (3)post_thanks_button
  • (1)post_thanks_javascript
  • (1)post_thanks_navbar_search
  • (3)post_thanks_postbit_info
  • (3)postbit
  • (3)postbit_onlinestatus
  • (3)postbit_wrapper
  • (1)spacer_close
  • (1)spacer_open
  • (1)tagbit_wrapper 

Phrase Groups Available:
  • global
  • inlinemod
  • postbit
  • posting
  • reputationlevel
  • showthread
Included Files:
  • ./showthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/functions_bigthree.php
  • ./includes/class_postbit.php
  • ./includes/class_bbcode.php
  • ./includes/functions_reputation.php
  • ./includes/functions_post_thanks.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • showthread_start
  • showthread_getinfo
  • forumjump
  • showthread_post_start
  • showthread_query_postids
  • showthread_query
  • bbcode_fetch_tags
  • bbcode_create
  • showthread_postbit_create
  • postbit_factory
  • postbit_display_start
  • post_thanks_function_post_thanks_off_start
  • post_thanks_function_post_thanks_off_end
  • post_thanks_function_fetch_thanks_start
  • post_thanks_function_fetch_thanks_end
  • post_thanks_function_thanked_already_start
  • post_thanks_function_thanked_already_end
  • fetch_musername
  • postbit_imicons
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • postbit_display_complete
  • post_thanks_function_can_thank_this_post_start
  • tag_fetchbit_complete
  • forumrules
  • navbits
  • navbits_complete
  • showthread_complete