Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does K2 Server fail to load an ODBC collection defined as anonymous by Verity?

April 26, 2017anonymous collection defined fail k2 load ODBC server verity

0

Posted

Why does K2 Server fail to load an ODBC collection defined as anonymous by Verity?

1 Answer

0

Posted

/P> For a successful anonymous ODBC collection setup, the following must be configured properly: All ODBC gateway repositories must be configured as secure. This means the SecurityField, in odbcmon.cfg, for all DSNs should be set to 1. An anonymous user for all repositories must exist in the credentials database (cred.dat) for that collection. If the style set is created using the K2 StyleSet Editor, all starting points must be configured as anonymous with valid database credentials. If the style set is manually configured, an anonymous entry for each repository must exist in credentials file. K2 Server must be configured to load this collection as anonymous. The anonymous setting is specified on the Collection Properties dialog in K2 Dashboard. For manual configuration, documentAccess for this collection must be set to anonymous.