You are viewing limited content. For full access, please sign in.

Announcement

Announcement

Deprecation Schedule for pre-release “v1-alpha” Laserfiche API Routes

posted on August 26

The Laserfiche API “v1-alpha” routes are being deprecated and will be deactivated on December 1st, 2022.  The deprecated routes contain “v1-alpha” in the URL.  (see: https://api.laserfiche.com/repository/swagger/index.html?urls.primaryName=v1-alpha)

Please update your code to reference the released version “v1” Laserfiche API routes. (see: https://api.laserfiche.com/repository/swagger/index.html?urls.primaryName=v1).

To simplify the use of our Rest APIs, Laserfiche is supporting publicly available client libraries via NPM and NuGet. See Laserfiche API developer documentation at https://developer.laserfiche.com/libraries.html for more details.

5 0

Replies

replied on August 30

Hi Andrew, thanks for the advanced notice.  We're using the v1-alpha endpoint https://api.laserfiche.ca/repository/v1-alpha/Repositories/r-xxxxx/AccessTokens/Create?createCookie=false&customerId=xxxxxxxxxxxxx

 

Can you guide us on the correct usage once the alpha version retires? We are using power automate for api calls into LF, passing the service principle username and password to return an authorization token.

Then we create a folder https://api.laserfiche.ca/repository/v1-alpha/Repositories/r-xxxxxxx/Entries/xxx/Laserfiche.Repository.Folder/children?autoRename=true

 

Then we populate field meta https://api.laserfiche.ca/repository/v1-alpha/Repositories/r-xxxxxx/Entries/@{outputs('Folder_EntryID')}/template

 

One more question, the service principle accounts expire after just three months meaning we must create new keys and update the web requests.  Is there a more resilient method we could use?

0 0
replied on September 1 Show version history

Hi Sean,

The short answer for a Service OAuth App is:
1)    Use Token endpoint (grant_type = client_credentials) to obtain an Access Token using the Access Keys exported from your Developer Console – App Configuration
2)    Use the Access Token value in Authorization header to access Repository API
3)    If HTTP 401 response (usually due to token expired) go to step 1 to get a new token an retry

For the longer answer, we’ll provide a more detailed guide in Laserfiche Developer Portal and update this post when ready.


Regarding your second question, Service Principal Key Expiration is configurable and can be disabled.

0 0
replied on September 13 Show version history

Hi Paulo, we've been all through the links you sent but don't get it sorry. Can we see a worked example or something to follow?  Are we still able to use our service principle keys to generate a token? We don't understand this registration concept properly?  The clock is ticking on the retirement date and we have live customers with dependencies on the v1-alpha end point - can we get some help to cut over?

0 0
replied on September 13 Show version history

Sean, I understand your confusion and we are working on a more detailed guide that should help.  Also, we will most definitely ensure that the v1-alpha deprecation doesn't impact your customers.  Hopefully we will have something for you soon!

0 0
replied on September 14

OK, as long as there is some flexibility around the end off v1-alpha, ie please don't deactivate it without giving us enough time to implement the guide - once it becomes available. It might be necessary to extend the cut off by some time if there is a delay in the guide -  is that agreed?

0 0
replied on September 26

Hi, we have another api connection to set up with Laserfiche cloud and would really appreciate access to that guide, even in a draft format or could there be a quick remote meeting with our guys to understand what work is required? If its better we wait it out then can you clarify the assurance that our customers wont be impacted by v1-alpha shutdown.  Can we understand this means the shutdown will not proceed until there has been sufficient time for an orderly transition to occur?   We are keen to cooperate with the transition, we just want to ensure we are communicating our concern the announced date is rapidly approaching and while we wait, we are building additional connections that will need to be changed to accommodate the new process - what ever that becomes. thanks and best wishes for a successful transition

0 0
replied on September 27

We will ensure that existing users of v1-alpha are fully migrated before we actually shut down that endpoint.  I will reach out to you via email so we can discuss in more detail.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.