nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Authentication Token Expiration Methodolgy

Steve_Hindmarsh

I understand that checking the authentication token expiry time on every request to see whether it needs renewing is the implementation that OpenText have used for authentication token management.

I am unhappy with this as it means I need to mainatin a reference to the username and the password which I wish to discard after the initial login which obtaines the token. This provides a very secure design model.

Question:

Can Content Server be configured so as the authentication token expiration date time is refreshed to say 30 minutes after the current request (a sliding expiration mechanism) or are we stuck with this rather inflexible absolute expiry time needing to be checked on every request?

Thank you

Find more posts tagged with

Comments

Brad_Ceballo

This is logged as bug #LESAPI-578, which is still open and unresolved.

Content Server 10+ can be configured this way, but the API ignores the setting and never updates tokens.

Brad

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Wednesday, February 06, 2013 8:07 AM
To: eLink Recipient
Subject: Authentication Token Expiration Methodolgy

Authentication Token Expiration Methodolgy

Posted bysteve.hindmarsh@pbworld.com (Hindmarsh, Steve) On 02-06-2013 08:01

I understand that checking the authentication token expiry time on every request to see whether it needs renewing is the implementation that OpenText have used for authentication token management.

Question:

Thank you

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Steve_Hindmarsh

I can't find anything relating to that reference number?

Do you have a link to it?

Thanks very much Brad

Brad_Ceballo

Bug numbers can’t be tracked externally.

You can check the Release Notes when Cumulative Updates and new versions come out to see if it’s fixed. It will be listed if it’s fixed.

You can also periodically request updates fromsupport@opentext.com.

Brad

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Wednesday, February 06, 2013 11:04 AM
To: eLink Recipient
Subject: RE Authentication Token Expiration Methodolgy

RE Authentication Token Expiration Methodolgy

Posted bysteve.hindmarsh@pbworld.com (Hindmarsh, Steve) On 02-06-2013 11:01

I can't find anything relating to that reference number?

Do you have a link to it?

Thanks very much Brad

[To post a comment, use the normal reply function]
Topic:	Authentication Token Expiration Methodolgy
Forum:	Content Web Services Forum
Content Server:	Knowledge Center