Author: Niamh Cassidy

How to “De-unify” a UNIFIED C•CURE/victor System

Warning – Level 2 Document – Please Do Not Distribute Article ID: SWH-KB-000036217 Steps Backup the database. Install victor on to a new system. License this system for non-unified victor. Restore this database over the victor database, then repair (so the Application Server records are correct). You now have a standalone victor system. On the… Continue reading How to “De-unify” a UNIFIED C•CURE/victor System

Card Only vs Extended CHUID Formats for long card numbers

Warning – Level 2 Document – Please Do Not Distribute Article ID: SWH-KB-000034825 Problem When the Card Only CHUID format is used for a credential, it allows for maximum card number of 10 digits, but also the maximum integer that can be derived in 32 bits.  Although card # 9999999999 is 10 digits long, in… Continue reading Card Only vs Extended CHUID Formats for long card numbers

C•CURE 9000 Legacy Maps will no longer be available as of C•CURE 9000 v3.10

Article ID: SWH-KB-0037469 Issue Starting in C•CURE 9000 v3.10, the older Legacy MAP format (version 2.60 and older) will no longer be available. Any Legacy MAP configurations that still exist in C•CURE 9000 systems prior to version 3.10 will no longer be available once the system has been upgraded to C•CURE 9000 v3.10. Solution Ensure… Continue reading C•CURE 9000 Legacy Maps will no longer be available as of C•CURE 9000 v3.10

Password column in ACVSCORE.Access.iStarController table for iSTAR Ultra G2 and Edge G2 shows Username in clear text

Warning – Level 2 Document – Please Do Not Distribute Article ID: SWH-KB-000037525 Problem C•CURE 9000 stores the unencrypted UserName in the password field and the actual password in the Token field. The Token field is encrypted. The UserName is not. Cause We do not encrypt username anywhere else in any other table. This has… Continue reading Password column in ACVSCORE.Access.iStarController table for iSTAR Ultra G2 and Edge G2 shows Username in clear text