Andrew N
- Login: red-tux
- Email: nelsonab@red-tux.net
- Registered on: 07/14/2014
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 1 | 1 |
Activity
08/27/2014
- 08:02 AM Foreman Revision add3bbdd (foreman): fixes #6205 Changed regex to parse CNs from SSL DNs on separator chars
- (cherry picked from commit 2821b5e250d2f311e2070c41879720f8745507cf)
08/15/2014
- 11:02 AM Foreman Bug #6205 (Closed): Custom SSL client cert for smart proxy based auth doesn't split CN correctly
- Applied in changeset commit:2821b5e250d2f311e2070c41879720f8745507cf.
- 09:25 AM Foreman Revision 2821b5e2 (foreman): fixes #6205 Changed regex to parse CNs from SSL DNs on separator chars
08/11/2014
- 11:39 AM Foreman Bug #6205: Custom SSL client cert for smart proxy based auth doesn't split CN correctly
- Pull request #1678 created.
- 11:30 AM Foreman Bug #6205: Custom SSL client cert for smart proxy based auth doesn't split CN correctly
- Ohad, Ori
I've almost got a pull request done, but I'm wondering if we might be going about this all wrong. I kno... - 11:16 AM Foreman Bug #6205: Custom SSL client cert for smart proxy based auth doesn't split CN correctly
- Ori,
I'll see what I can do to put a pull together for it. Are there any appropriate pages I should read first? - 11:13 AM Smart Proxy Refactor #7010: Improve Error/Debug Log messaging
- I think setting the scope to only DHCP proxy misses the point of what I opened the bug for. The intent was to help e...
08/10/2014
- 12:49 PM Smart Proxy Refactor #7010: Improve Error/Debug Log messaging
- Turns out issue was related to permissions. Perhaps it would be useful to break up configuration and access checks i...
- 12:21 PM Smart Proxy Refactor #7010 (Resolved): Improve Error/Debug Log messaging
- I'm trying to get a DHCP smart proxy configured on RHEL 6, but the default error message is practically useless. The...
07/14/2014
- 03:17 PM Foreman Bug #6205: Custom SSL client cert for smart proxy based auth doesn't split CN correctly
- I'm trying to get Foreman installed at a client site and have been running into the above bug, but for different reas...
Also available in: Atom