From the integrators
Several folks have told us they can't import primary card numbers when they're using the Custom Sync Module. There is in fact an advanced config key to help with this and we have added the additional information to the knowledge base article. Here are the details for the curious.
- By default the custom sync program should only provide the following user details (there was incorrect/confusing information on the KB about this)
- Username
- Full Name
- Email Address
- Department
- Office
- However, if the advanced configuration key user-source.update-user-details-card-id is set to "Y" then additional user details can be provided:
- Username, Full Name, Email Address, Department, Office, followed by
- PrimaryCardNumber
- Other Emails
- SecondaryCardNumber
- User Alias (a.k.a secondary user name)
- Home Directory
- PIN
Note: If not needed, any field (except the user name) can be set to zero length value ("").
We've updated the example Go and Python programs (as well as the KB article above) to show how this works. The example programs now call the web services API to discover the value of user-source.update-user-details-card-id and change behavior accordingly. However in production you would probably make that behavior a configuration option in the program to avoid the overhead of an API call every time custom sync program is run.
If you have any questions about this, or need any other integration information, please contact us at integration-dev-support@papercut.com. You can also ask questions on the Google Group.