Skip to main content

Hello.

We have installed assyst 11.8.2 in a non-production environment for testing, and are having an issue with the assystNET page not loading. We have two sets of web servers which authenticate differently, and all applications (assystnet, assystnetmob) on both sectors is having the issue.

 

assystWeb login works fine.

 

When a client attempts to access assystNET, the following error occurs in the server.log:

 

2024-08-21 09:11:17,455 ERROR Ocom.axiossystems.assyst.dao.security.CSGFilter] (default task-2) CheckDtos : unable to set property => csg

 

Here is a screenshot of the error:

 

We have tried numerous different authentication methods (LDAP, Azure SAML), and the same issue occurs.

I have opened an incident with assyst support, but they have yet to be able to prvovide any advise.

 

Has anyone else seen this with 11.8.2?

 

Thanks,

 

Duncan

 

We’re on 11.7 but it looks like it is requiring CSG to not be NULL, it needs to filter on that.  We do not use CSG.  I’d suspect that you have one or more users with a CSG value and thus it is now required.


Hi. Thanks for the quick reply, but there should not be any CSG issues. We do have CSGs in use (always have), and all of our users are CSG’d correctly. Unless the 11.8.2 database upgrade tool did something with the CSG data, there should be nothing different between the new installation and our current 11.6.3 production system.


Hello Duncan,

I was going to recommend that you contact our support team for further investigation, but I noticed you’ve already done so (Ref 417340 ). 

I believe the investigation is moving forward, and you can expect feedback soon.

Kind Regards,
Caroline


FYI in case anyone is following this, the error is caused by a known defect and is being tracked by Problem ticket  P16554 .

IFS has indicated that this defect will be fixed in the next release (11.8.3), which is scheduled for release on September 24th.

 


Hello all. Could I ask if the matter has been resolved? We are currently under Version 11.6.1 and are looking to upgrade to version 11.8.3 soon? Thank you.


Hi. Yes, this issue has been resolved in 11.8.3.

https://community.ifs.com/assyst-release-notes-364/assyst-11-8-3-release-notes-52534

Duncan

 

 


Reply