Signature Portal Security overview

This section contains general information and tips about Signature Portal Security.

• The objects (and meta) need to be created only once per company, but they can be run additional times without destroying any data.
• Installation of SQL objects is transactional; if the install fails, all objects are removed.
• ODBC isn't used. When you're prompted for server names, enter the actual server name, not an ODBC name.
• Signature Portal Security uses Integrated Windows Authentication. You can change this in the PortalSecurity.exe.config file.
• Signature Portal Security can support multiple companies. You can select different companies or add companies as needed.
• Signature Portal Security contains all the SQL objects. You can add new companies without installation media.
• When you set up security for the portals, grant permissions before you load a visual template.
• Visual templates rely on data permissions and won't load correctly if the data permissions aren't set.
• Job Cost creates and maintains SQL logins. The users are associated with employees. A single user can be associated with an employee in more than one company.
• The assignment of the SQL user needs to be set to none for all companies before a user can be deleted.
• Signature Portal Security application errors are sent to the Windows Event Log (WennSoft).