Niels Liisberg
Niels Liisberg
It all ready have support for JWT. So you can use I.e. KeyCloak for SSO tir. 21. mar. 2023 kl. 15.56 skrev JuanmaAlcudia ***@***.***>: > More and more new applications...
Ok - so it seams like the stream-feature either on noxDb or in ILEastic is doing something "undocumented" ... I'll take a look. Thank you for the Feedback
Absolutely - However SSL/TLS for HTTPS is a plan for the future ...The Apache / Nginx revese proxy is the solution for now
.. Actually - the SSL/TLS code is in the project now. I have, however, not made it active yet...
ILEastic is using the option 51 ILE C compiler, however it has a dependency to noxDb which also is using the CPP ( option 52). But as far as I...
Thanks for the input. I will discuss this the group and find a solution. The JWT is split to atoms in the current support. However JWK is a different animal...
It is correct, however some times it can be useful to start it serialized - so the "servlet" is called sequentially. ( like it was popping data from a data...
Well - we actually use this feature in out IceBreak server that "also" has this feature. Typillaly for retrofitting old RPG (batch) code to ba able to do transactions. Yes...
Also for FASTCGI - only one process is valid.... when we come to FASTCGI ..
You should be able to do response.status = IL_HTTP_NO_CONTENT; return .. otherwise it is a bug On Thu, Jul 30, 2020 at 11:27 AM m1h43l wrote: > In many cases...