Restricted Token from /SessionConetxt Cancel The title field is required!

1. Sascha Zehringer

   

   9 posts
   Registered:
   28 Oct 2022
   31 Oct 2022

   Link to this post

   Dear Consultingwerk-Team,
   
   since we use many "SmartSecurityTokens" (over 900) and some users got assigned every token, they got a lot of "SmartSecurtiyAssignments". And since these are loaded via the "SessionContext"-REST in a character-string, we are getting errors from "Progress.Lang.SysError", because the Character extended the allowed byte size.
   
   Is there a way to either disable this functionality and load it from a different REST 
   or can we somehow change the datatype without other big changes
   or is there an other REST which would suit our requiremenst better?
   
   If nothing of these options are possible, i would code a "SessionContextWebHandler" by myself as a Handler in the "openedge.properties", but is there something i should be aware of?
   
   Thank you in advance. 
   
   Regards
   Sascha Zehringer
2. Mike Fechner

   

   342 posts
   Registered:
   14 Sep 2016
   31 Oct 2022 in reply to Sascha Zehringer

   Link to this post

   Do you actually need the restricted tokens in the session context on the client? Or are they used on the backend only?
   
   For the actual error, please log a support ticket (JIRA service desk) and include the complete error message and stack trace to investigate. 
   
   Regardless of the answer to the first question, we should not error.
3. Sascha Zehringer

   

   9 posts
   Registered:
   28 Oct 2022
   31 Oct 2022 in reply to Mike Fechner

   Link to this post

   We do not need them in our frontend. We use them in the Backend only. There we just access the tabels.
   
   Okay, i'll do that.
4. Mike Fechner

   

   342 posts
   Registered:
   14 Sep 2016
   31 Oct 2022 in reply to Sascha Zehringer

   Link to this post

   In that case, we should be able to first workaround the issue by makinh sure the list if not getting too long. 
   
   In a second steps, we'd make sure that we return a too long list of restricted tokens in a suitable form. 
5. Sascha Zehringer

   

   9 posts
   Registered:
   28 Oct 2022
   Answered

   15 Nov 2022

   Link to this post

   This Bug was solved in SCL-3848.