I have a custom extension for logging.. do you want to test and provide feedback?
On Tue, Jul 14, 2026 at 2:40 PM Brad Turnbough < [email protected]> wrote: > Just the RADIUS plugin so I can auth against my pre-exsiting MFA back end. > > > > > > > > > Thanks, > Brad > > *From:* Sean Hulbert <[email protected]> > *Sent:* Tuesday, July 14, 2026 1:33 PM > *To:* [email protected] > *Subject:* [DKIM-Failure]Re: Guac Logging > > > > *CAUTION: External Sender * Do not click links or open attachments unless > you recognize the sender and know the content is safe. > *Report suspicious emails to the IT Help Desk.* > > Are you using MFA extension ? > > *Thank You* > Sean Hulbert > > > Industry's most secure CMMC/iTAR virtual desktops! > > > *CMMC Level 2 Certified* > > System Award Management > *CAGE: 8AUV4* > *SAM ID: UMJLJ8A7BMT3* > > AFCEA San Francisco Chapter President > If you have heard of a hacker by name, he/she has failed, fear the hacker > you haven’t heard of! > > CONFIDENTIALITY NOTICE: This communication with its contents may contain > confidential and/or legally privileged information. It is solely for the > use of the intended recipient(s). Unauthorized interception, review, use or > disclosure is prohibited and may violate applicable laws including the > Electronic Communications Privacy Act. If you are not the intended > recipient, please contact the sender and destroy all copies of the > communication. Content within this email communication is not legally > binding as a contract and no promises are guaranteed unless in a formal > contract outside this email communication. > > igitur qui desiderat pacem, praeparet bellum!!! > > Epitoma Rei Militaris > > > > On 7/14/2026 11:30 AM, Barnhart, Steven via user wrote: > > Agreed that would be helpful. But even more helpful would be finally > logging a unique identifier for a connection and to tie logs from guacd to > the guacamole app ☹️ > > > > --Steve > > *From: *Brad Turnbough <[email protected]> > <[email protected]> > *Date: *Tuesday, July 14, 2026 at 2:26 PM > *To: *[email protected] <[email protected]> > <[email protected]> > *Subject: *Guac Logging > > *This Message Is From an External Sender* > > This message came from outside your organization. > > Report Suspicious > <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/KGKeukY!vwQf06ZtD6YgJRdwH4-k180UfIUBzWB9qGiOy52bk5PKBqB6X2cRq4JI96VE9Ht1GZl_rI7-gzG7Yk16VleSC-UbyIFKTcJCt5h9pILdEGleqbKum3WPZPl3-W8TfOiCf58ku4n9tlOqUoTP$> > > > > I have logging working pretty well, but there is one thing that still > bothers me. > > > > > > For example: > > Jul. 14, 2026 1:22:38.911 2026-07-14T06:22:37,517Z > [https-openssl-apr-443-exec-6] INFO o.a.g.tunnel.TunnelRequestService - > User "USERABC" connected to connection "123". > > Jul. 14, 2026 1:22:38.911 2026-07-14T06:22:37,524Z > [https-openssl-apr-443-exec-25] INFO o.a.g.tunnel.TunnelRequestService - > User "USERABC" connected to connection "132". > > > > > > Can guac be configured to log the connection name in addition to the > connection number of “123” or “132” > > I have the skills to write the query to get the info out of the database > manually, but I figured the logger should at least log the connection name > for immediate analysis purposes. > > > > Thanks, > > Brad > > > > > Thank you, > > *Brad Turnbough* > Senior Technology Analyst > > > > P: 309.272.2739 > www.betterbanks.com > <https://urldefense.com/v3/__http:/www.betterbanks.com/__;!!KGKeukY!xcmGJK-IZseQDKssFP5KaONgdDQgJaioArmBt6dmONhg7iTIifwlCJcWhqnECmYsbWXuZGfbP7YEIZ2FK02PtVz0ZvmIJPfq7ZE$> > www.statestreetbank.com > <https://urldefense.com/v3/__http:/www.statestreetbank.com__;!!KGKeukY!xcmGJK-IZseQDKssFP5KaONgdDQgJaioArmBt6dmONhg7iTIifwlCJcWhqnECmYsbWXuZGfbP7YEIZ2FK02PtVz0ZvmIUy-rxqg$> > > > NOTICE: The information contained in this email and any document attached > hereto is intended only for the named recipient(s). If you are not the > intended recipient, nor the employee or agent responsible for delivering > this message in confidence to the intended recipient(s), you are hereby > notified that you have received this transmittal in error, and any review, > dissemination, distribution or copying of this transmittal or its > attachments is strictly prohibited. If you have received this transmittal > and/or attachments in error, please notify me immediately by reply e-mail > and then delete this message, including any attachments. > >
