Question

Question regarding Keyed Integrator licenses - How to deploy Read/Write vs. Read-Only

Directory Server SDK Deployment Tookit Integrations Licensing

Updated January 30

asked on November 4, 2022

We have a client who has separately purchased two different "Keyed Concurrent" licenses. One with 100 Read-Only connections, and one with 75 Read/Write connections.

They've activated the licenses in LFDS and they're both showing under the same Application Key (see attached screenshot). The question now is, how are we to dole out the the correct version of the license (R/W vs R/O)? Since they are tied to the same Application key, I don't see how we prevent an application from consuming a Read/Write license if we only want it to be Read Only, and vice versa.

I opened a support case with LF but they suggested that I post to Answers in-hopes that a LF Developer would respond.

Thanks,

Mike

Keyed Integrator License.jpg (26.99 KB)

| Download

0 0

Answer

APPROVED ANSWER SELECTED ANSWER

replied on November 4, 2022 • Show version history

Update Jan 30, 2024: The information below about setting "Session.IsReadOnly = true" is incorrect/incomplete.

To use a read-only session, the account must be set to be Read-Only in the Laserfiche Administration Console, and must not have the "Manage Trustees" privilege as that negates the Read-Only account property.

----------------

I believe you set the Session.IsReadOnly property to "true" before the login attempt. Create a basic Session object, set the IsReadOnly prop, and then call one of the LogIn() methods. See below.

Alternatively, I think you can also request that your Keyed Integration Licenses be re-issued under two different Applications Keys. You'd have to make that request to Sales, who would check with our Orders/Licensing team. The request would be something like:
"We would like the KILs split onto two different application keys, one with all the Read-write connections, one with all the Read-only connections. Please name them "*-App-Dev-ReadWrite" (75 RW connections) and "*-App-Dev-ReadOnly" (100 RO connections)."

If they can make that change, you'll need to deallocate any KIL connections currently assigned to LFS instances, then refresh/renew your primary license in LFDS, then re-allocate connections from the new keys to LFS in LFDS again, then download and replace the LFS license(s).

3 0

Replies

replied on November 4, 2022

Great info, thank you Sam!

0 0

You are not allowed to follow up in this post.

Question

Question

Question regarding Keyed Integrator licenses - How to deploy Read/Write vs. Read-Only

Answer

Replies

Sign in to reply to this post.