EDouglas
Member
Issue : Orphan Sessions on AIS Server
Background; using JDE REST APIs tokenrequest and tokenrequest/logout
1. called manually via Postman using either Basic Auth or username/password - AIS Sessions are terminated as they should be
2. called via a .NET Core 6 Minimal API wrapper using HttpClient - tokenrequest/logout - leaves an AIS Session active
Development; using the .NET Core 6 Minimal API: calling tokenrequest, appstack (open, execute, close), tokenrequest/logout for multiple APIs works fine and performs as expected ...
adding and inserting records as required.
Running the API via Postman in test we noticed, via AIS Server Manager, that the AIS Sessions were not being terminated.
Stripped out all AppStack code, so the test API is running just tokenrequest and tokenrequest/logout.
Environment; Windows Server 2016, IIS Server
JDE E1 9.2.2.8 : AIS and HTML Servers
Does anyone have experience in this arena?
Any help would be very much appreciated.
Thank You,
Eric
Background; using JDE REST APIs tokenrequest and tokenrequest/logout
1. called manually via Postman using either Basic Auth or username/password - AIS Sessions are terminated as they should be
2. called via a .NET Core 6 Minimal API wrapper using HttpClient - tokenrequest/logout - leaves an AIS Session active
Development; using the .NET Core 6 Minimal API: calling tokenrequest, appstack (open, execute, close), tokenrequest/logout for multiple APIs works fine and performs as expected ...
adding and inserting records as required.
Running the API via Postman in test we noticed, via AIS Server Manager, that the AIS Sessions were not being terminated.
Stripped out all AppStack code, so the test API is running just tokenrequest and tokenrequest/logout.
Environment; Windows Server 2016, IIS Server
JDE E1 9.2.2.8 : AIS and HTML Servers
Does anyone have experience in this arena?
Any help would be very much appreciated.
Thank You,
Eric