Solutions for OA system and domain integration

OA system and domain integration our company requires that the OA system be integrated with the WINDOWS domain. The OA system is written in JAVA or PHP. after integration, the effect is: if I log on to the domain, I can use the OA system, in other words, I do not need to enter the account and password for the OA system. here, the difficulty is that the web page uses session to determine the OA system and domain integration of the requester.
Our company requires that the OA system be integrated with the WINDOWS domain. The OA system is written in JAVA or PHP. after integration, the effect is: if I log on to the domain, I can use the OA system, in other words, I do not need to enter the account and password in the OA system. here, the difficulty is that the web page uses session to determine the identity of the requester. if the session is set to expire too short, the password may be entered again after a short expiration time. if the session is set too long, a large amount of server resources will be wasted. Is there a way to implement it within the normal SESSION time, as long as I can use the OA system in the domain, it will not expire. it will expire after I exit the domain.

In fact, the ultimate goal is to use the domain ID to use the OA system, and the OA login page will not exist. Hope the experts can provide a good solution. thank you.


------ Solution --------------------
There is still hope for ASP or. net, and there is no hope for java.
------ Solution --------------------
Try using cookies
------ Solution --------------------
You can record the domain ID and password in the database, and then judge in it. after logging on to the domain, check whether the user name currently logged on is consistent with that in the database, if they are consistent, the logon is successful and the value is written to the session.
------ Solution --------------------
If your company's ip address is allocated through dhcp through the Domain controller, you can use the ip address to determine whether it is safe for the company.
------ Solution --------------------
I don't think this is necessary either. Now that all personnel are licensed. You don't have to judge in the OA system. You only need to record the corresponding ID after logging on to the user.