1,238
edits
Changes
From Pumping Station One
→What's next
=System Description=
=System Description=
*all production software is on a VM in our server closet and should be documented on the official [https://github.com/pumpingstationone PS1 Github]
*all production software is on a VM in our server closet and documented on the official [https://github.com/pumpingstationone PS1 Github]
*[membership.pumpingstationone.org The member management system], Wild Apricot, user has RFID fob entered into user profile. Can be by admin or self service, seperate multiple tags by a comma
*[membership.pumpingstationone.org The member management system], Wild Apricot, user has RFID fob entered into user profile. Can be by admin or self service, seperate multiple tags by a comma
*WA2AD goes down the list of all members in WA and does an active directory lookup to see if the member exists and verifies members status. If the user doesn't exist an AD user is created. It runs on our active directory controller (DC01), via Windows task scheduler every 5 mins. Ron uses a tool called "active directory explorer" to see all groups in users in AD.
*WA2AD goes down the list of all members in WA and does an active directory lookup to see if the member exists and verifies members status. If the user doesn't exist an AD user is created. It runs on our active directory controller (DC01), via Windows task scheduler every 5 mins. Ron uses a tool called "active directory explorer" to see all groups in users in AD.
*WA2AD handles computer authorization - it looks up the string associated with the "computer authorizations" checkbox in WA and puts the user in an AD groups that enables the user to log into the computer associated with that piece of equipment.
*WA2AD handles computer authorization - it looks up the string associated with the "computer authorizations" checkbox in WA and puts the user in an AD groups that enables the user to log into the computer associated with that piece of equipment.
*Active directory stores member status with the userAccountControl field - if a members is inactive their RFID fob and all computer logins are disabled.
*Active directory stores member status with the userAccountControl field - if a members is inactive their RFID fob and all computer logins are disabled.
*AD2RFID is a program that runs as a cron job everty 15 min on Glue, a centOS linux box.
*AD2RFID is a program that runs as a cron job everty 15 min on Glue, a centOS linux box. It only adds users to the board when they are new and explicitly diables them on the board when they are inactive members. It replaces all members every time it runs.
*AD2RFID does the Weigand conversion to the fob number to store on the controller board, which is what is compared to what the RFID readers at the door send to the control board.
*The IP address of the board is effectively static and is assigned via MAC address.
*The board occasionally hangs and AD2RFID times out after 1 minute of not receiving a reply from the board and waits for the next scheduled job to try again.
*Glue and the domain controller must be running for the data transfer process from WA to the board to work correctly.
=Troubleshooting=
*All RFID fob numbers must start with 00 - sometimes the reader reports numbers incorrectly - the number on the fob will be be the number in the RFID field in WA.
*Make sure the member has an active account
*Make sure the tags in RFID field are separated by a comma. All RFID tags are stored in otherPager field (which contains an array of numbers) in AD.
*https://technet.microsoft.com/en-us/library/cc720650(v=ws.10).aspx
*https://www.mssqltips.com/sqlservertip/4190/import-active-directory-data-to-a-sql-server-table/
=What's next=
=What's next=
*Writing a cron job to sync PS1Auth data (that members can add their RFID) to the RFID2 SQL database the door reader uses.
*Writing a cron job to sync PS1Auth data (that members can add their RFID) to the RFID2 SQL database the door reader uses.
*Create an Auto-it script that presses the upload button in the control software to send info from the SQL database to the controller.
*Create an Auto-it script that presses the upload button in the control software to send info from the SQL database to the controller.
==DEV2AD==
A wifi enabled microcontroller with an RFID reader makes a webservice call to Glue. Dev2AD is running on Glue and receives the call. DEV2AD validates that the tag is associated with the authorization for that tool. Currently the theory would be that DEV2AD would look at the AD group for a particular piece of equipment, grab the list of all users in that group, and search for a matching tag - if a tag matches then an activity will be initiated.
==Status==
==Status==
