Re: Log format access logs standard
%S did solve. Thanks to Mark. Thanks and Regards, Rinilnath Mobile#9786285451 On Tue, 7 Jun, 2022, 20:07 Jalaj Asher, wrote: > Can you try JSessionID ? > > -Original Message- > From: rinilnath r > Sent: Tuesday, June 7, 2022 7:25 AM > To: Tomcat Users List > Subject: Re: Log format access logs standard > > [You don't often get email from riniln...@gmail.com. Learn why this is > important at https://aka.ms/LearnAboutSenderIdentification ] > > Attention! - This email has originated from an External Source outside of > eClinicalWorks. Always use caution when opening attachments, clicking > links, or when responding to this email. If you feel this is a phishing > scam, please use the Phish Alert Report button in Outlook. > > > Thanks Mark, i corrected that by removing the > symbol > > But my next problem is to log the session ID I tried > x-H(requestSessionId), but it is not the correct. > Please help > > Thanks and Regards, > Rinilnath > Mobile#9786285451 > > On Tue, 7 Jun, 2022, 12:11 Mark Thomas, wrote: > > > On 07/06/2022 07:06, rinilnath r wrote: > > > Hi, > > > > > > What's the meaning of this? > > > %>s > > > > If that appears in the pattern attribute of an AccessLogValve then it > > is an error and you'll see the following in the access log: > > > > ???>???s > > > > Mark > > > > - > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains > confidential information belonging to the sender that is legally privileged > and proprietary and may be subject to protection under the law, including > the Health Insurance Portability and Accountability Act (HIPAA). If you are > not the intended recipient of this e-mail, you are prohibited from sharing, > copying, or otherwise using or disclosing its contents. If you have > received this e-mail in error, please notify the sender immediately by > reply e-mail and permanently delete this e-mail and any attachments without > reading, forwarding or saving them. Thank you. > > CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains > confidential information belonging to the sender that is legally privileged > and proprietary and may be subject to protection under the law, including > the Health Insurance Portability and Accountability Act (HIPAA). If you are > not the intended recipient of this e-mail, you are prohibited from sharing, > copying, or otherwise using or disclosing its contents. If you have > received this e-mail in error, please notify the sender immediately by > reply e-mail and permanently delete this e-mail and any attachments without > reading, forwarding or saving them. Thank you. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: LDAPS Configuration with Tomcat
Rakesh, On 6/6/22 09:54, rakesh meka wrote: Currently we are using an internal application which is deployed on windows server. And we use http which means we didn't configure SSL or TLS setup with application. The current application is using LDAP for user authentication which checks with active directory for verification . Can any one let me know how we can configure LDAPS now ? Should we need to configure the application with https before we enable LDAPS ? It doesn't matter in which order you do these. But if you need users to authenticate with your application, then encrypting that communication channel should be a top priority. Otherwise, anyone nearby on your network can read everyone's credentials, regardless of whether you are using LDAP or LDAPS. Or any other kind of credential-checking system. I tried changing the port to 636 but not successful. So need help if we can directly generate the certificate and place in somewhere in Tomcat directory ? You need to use an ldaps:// URL, not just change the port number. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Log format access logs standard
Can you try JSessionID ? -Original Message- From: rinilnath r Sent: Tuesday, June 7, 2022 7:25 AM To: Tomcat Users List Subject: Re: Log format access logs standard [You don't often get email from riniln...@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Attention! - This email has originated from an External Source outside of eClinicalWorks. Always use caution when opening attachments, clicking links, or when responding to this email. If you feel this is a phishing scam, please use the Phish Alert Report button in Outlook. Thanks Mark, i corrected that by removing the > symbol But my next problem is to log the session ID I tried x-H(requestSessionId), but it is not the correct. Please help Thanks and Regards, Rinilnath Mobile#9786285451 On Tue, 7 Jun, 2022, 12:11 Mark Thomas, wrote: > On 07/06/2022 07:06, rinilnath r wrote: > > Hi, > > > > What's the meaning of this? > > %>s > > If that appears in the pattern attribute of an AccessLogValve then it > is an error and you'll see the following in the access log: > > ???>???s > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains confidential information belonging to the sender that is legally privileged and proprietary and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act (HIPAA). If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains confidential information belonging to the sender that is legally privileged and proprietary and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act (HIPAA). If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Log format access logs standard
On 07/06/2022 12:24, rinilnath r wrote: Thanks Mark, i corrected that by removing the > symbol But my next problem is to log the session ID I tried x-H(requestSessionId), but it is not the correct. Please help That will only work with the ExtendedAccessLogValve and will record the session ID requested by the client, if any. If you want the actual session ID then you want: %S Note the upper case 'S' rather than lower case 's'. This will work with the standard AccessLogValve and the ExtendedAccessLogValve. Mark Thanks and Regards, Rinilnath Mobile#9786285451 On Tue, 7 Jun, 2022, 12:11 Mark Thomas, wrote: On 07/06/2022 07:06, rinilnath r wrote: Hi, What's the meaning of this? %>s If that appears in the pattern attribute of an AccessLogValve then it is an error and you'll see the following in the access log: ???>???s Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Log format access logs standard
Thanks Mark, i corrected that by removing the > symbol But my next problem is to log the session ID I tried x-H(requestSessionId), but it is not the correct. Please help Thanks and Regards, Rinilnath Mobile#9786285451 On Tue, 7 Jun, 2022, 12:11 Mark Thomas, wrote: > On 07/06/2022 07:06, rinilnath r wrote: > > Hi, > > > > What's the meaning of this? > > %>s > > If that appears in the pattern attribute of an AccessLogValve then it is > an error and you'll see the following in the access log: > > ???>???s > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Log format access logs standard
On 07/06/2022 07:06, rinilnath r wrote: Hi, What's the meaning of this? %>s If that appears in the pattern attribute of an AccessLogValve then it is an error and you'll see the following in the access log: ???>???s Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Log format access logs standard
Hi, What's the meaning of this? %>s Thanks and Regards, Rinilnath Mobile#9786285451
