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; } } }

Can you set the token from CWS to never expire?

(INACTIVE)_Nathan_Law

Currently I do a timespan check and re-authenticate, but it would be more efficient to either set the token to never expire on creation or set it to a sliding expiration. We have some bulk load processes and this is just another call that would be nice to be eliminated.

Also, is it possible to connect as Admin via CWS without the need for a token?

Find more posts tagged with

Comments

Carsten_Kulms

If CWS are deployed standalone then the token is the same as the authentication cookie used with the UI thus it is subject to the corresponding security settings; see https://knowledge.opentext.com/knowledge/piroot/llescor/v100009/llescor-h-agd/en/html/lleswba-h-agd-wba-confsecurity-bg.htm Please note that this setting affects both: end-user accessing the UI and CWS clients.The expiration can be configured as "sliding expiration" (expire x minutes after last request) but unfortunately this does not make its way through the web services layer so for CWS it behaves effectively as the "expire x minutes after log-in" setting. (There is already a bug report with the reference id "LESAPI-578" for this--you may like to be added to this; please contact OT Customer Support in this regard.)If CWS are deployed in RCS the answer is No.Regarding your second question: The answer is No. Authentication is mandatory, of course.

(INACTIVE)_Nathan_Law

thanks for the reply!