Question

Access Token Expiration Limit (Self-Hosted Laserfiche API Server)

Laserfiche API Self-Hosted Integrations How To

Updated April 26, 2024

asked on January 8, 2023 • Show version history

Hello community,

Hopping everyone is safe.

We would like to know how to disable the "Access Token Expiration Limit" so that the generated token value of "Request for an access token" for "Bearer" will never expired?

Also where we can get the "Keyed Concurrent License" if it has?

Regards.

0 0

Replies

replied on January 10, 2023

Rafael,

Do you mind sharing more details on how you are using our API? Are you leveraging our client libraries (our client libraries automatically handle the process of refreshing tokens) or a 3rd party integration platform?

In regard to "Keyed Concurrent License", you can reach out to your territory manager and they can assist you.

0 0

View 3 previous replies

replied on January 10, 2023

Hi Andrew,

We use a 3rd party integration platform like "POSTMAN."
We used the token from the API server, and after a few minutes, the token that had been generated already expired, even in Laserfiche API Server. Also, we need to prove to our prospective client that Laserfihce can integrate into a 3rd party app using the API.

0 0

replied on January 16, 2023

Rafael,

In your 3rd party platform you will need to detect when the token has timed-out and initiate a call to retrieve a new token. This process is automatically handled by our client libraries, but if you can't use them, you'll need to add similar logic in your platform of choice.

Andrew

0 0

replied on January 19, 2023

Hi Andrew

Thank you for your feedback it helps,

Also, may we ask if Laserfiche Self-Hosted API is included in the basic package of Laserfiche Products? or it's a separate module where can we ask for the price?

Thanks

0 0

replied on January 20, 2023

Rafael,

The Laserfiche API Server is available for download to all self-hosted customers via our Support site.

Best,

Andrew

0 0

replied on January 22, 2023

Hi Andrew,

Thank you for the info.

Regards,

Matt Andrew of Metasystems Inc.

0 0

replied on April 26, 2024

I believe adding a parameterless constructor to the FileParameter class of V1 (Self-hosted) from your side may resolve the error below. I am getting this error while implementing a wrapper against self-hosted API V1.

I am trying to create a new Restful API that takes FileParameter as one field of the view model class during Model Binding.

System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'Laserfiche.Repository.Api.Client.FileParameter'. Path: $.fileParameter | LineNumber: 49 | BytePositionInLine: 20.
 ---> System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'Laserfiche.Repository.Api.Client.FileParameter'.

0 0

replied on February 19, 2024

Hi Andrew,

I am trying to make a call to the Self-Hosted Laserfiche API Server from our console app and getting no response. It did not log any error either. The "lf-sample-repository-api-dotnet-srv" code is not working as intended and I have to generate the client using NSWAG. I think that's working as well. Is there a sample client code to play with?

0 0

View 2 previous replies

replied on February 20, 2024

Hi,

I verified that https://github.com/Laserfiche/lf-sample-repository-api-dotnet-srv/tree/v1 (using v1 client libraries) works with Self-Hosted API Server . Make sure you select v1 since Repository API v2 are currently Cloud only. No need to generate a new client.

1 0

replied on February 23, 2024

Paolo,

I could be able to import the documents. I have another question. will the API be able to handle the volume 30K-100+K pdf documents per day? Will we need to multi-thread, can we if we need to?

0 0

replied on February 23, 2024

The API Server itself should not be a bottleneck, it mostly depends on the underlining infrastructure running Laserfiche Server, size of the PDF, concurrency, other load, ...

Multi-thread is an option. YMMV.

0 0

replied on February 26, 2024

We have a Laserfiche Server (1 server) per environment. If we want to have more than one LF App Server, how can we connect to these servers from LF Repository API which is load balanced. Can we load balance the LF App servers that contains Import Agent installed on them?

This is the setting that connect the Repo API to LF App Server as you know:

"LaserficheServerName": "xxxxx.yyyy.com"

Note that, xxxxx.yyyy.com is the FQDN of LF App Server ( 1 server ). Can we connect to two LF App Servers that contains Import Agents? if so how?

0 0

replied on April 26, 2024

I am trying to create a new Restful API that takes FileParameter as one field of the view model class during Model Binding.

System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'Laserfiche.Repository.Api.Client.FileParameter'. Path: $.fileParameter | LineNumber: 49 | BytePositionInLine: 20.
 ---> System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'Laserfiche.Repository.Api.Client.FileParameter'.

0 0

You are not allowed to follow up in this post.

Question

Question

Access Token Expiration Limit (Self-Hosted Laserfiche API Server)

Replies

Sign in to reply to this post.