Skip to main content
Solved

User is still able to access application even though end date is filled in and is expired.

  • November 20, 2025
  • 2 replies
  • 24 views
L
Apprentice
Forum|alt.badge.img+1

The thinkwise documentation states that the end date of a user in the IAM controls the access of a user to the application. However, the user is still able to access the application after i fill in the end date. 

If i fill in the end dates in the user group of which the user is a member of then the user has no access to the application. I expected the end date on user level would be the primary end date. Am i mistaken about what the end date of a user does?

 

We are using windows GUI and version 2025.1. The user is not an admin or have any other role in the IAM and authentication is through windows.

Best answer by Mark Jongeling

Hi Ling Wu,

The 2-tier authentication has been revised in 2025.2, and the Begins on and Ends on fields on User do restrict a user to be able to log in through the Windows GUI.

However, in a 2-tier environment, setting the Ends on field would not prevent the user from accessing the database directly though an IDE for example. 

To prevent a user from logging in through the Windows GUI (2-tier) in 2025.1, you will have to enter the Ends on field for the user groups the user is assigned to:

IAM > Authorization > User groups > Users

 

Note, the 3-tier architecture did already listen to the Begins on and Ends on fields at User level. If you were using Universal GUI, your users could not log in if the timestamp of Ends on has passed.

2 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Mark Jongeling
  • Administrator
  • Answer
  • November 24, 2025

Hi Ling Wu,

The 2-tier authentication has been revised in 2025.2, and the Begins on and Ends on fields on User do restrict a user to be able to log in through the Windows GUI.

However, in a 2-tier environment, setting the Ends on field would not prevent the user from accessing the database directly though an IDE for example. 

To prevent a user from logging in through the Windows GUI (2-tier) in 2025.1, you will have to enter the Ends on field for the user groups the user is assigned to:

IAM > Authorization > User groups > Users

 

Note, the 3-tier architecture did already listen to the Begins on and Ends on fields at User level. If you were using Universal GUI, your users could not log in if the timestamp of Ends on has passed.

"Wake me up before you low-code"
L
Apprentice
Forum|alt.badge.img+1
  • Ling WuApprentice
  • Author
  • Apprentice
  • November 24, 2025

Thanks for the information. I did check the platform release notes to see if anything has changed since version 2025.1 but could not find anything. Might have overlooked it.

Terms & ConditionsCookie settingsAccessibility statement