After intensively tesing some of the authentication agents there are some open questions / feature requests ?
Windows Authentication Client "SAA"
Works obviously quite nice, but has 2 drawbacks:
1. It looses from time to time after a while connection and requires manual login (go to credentials again and save them again). Reconnection should occur automatically rthaer than manually in my eyes...
2. It has to be installed per User (if multiple logins exist on a client). Client Installation should happen for all profiles, and credetials should be saved per login / user in the profile)
Linux Authentication Client "CAA"
Also works obviously nice, also with automatic startup as daemon from the .profile at user login works flawless. Also here 2 questions / feature requests
1. Is there a way to install or start the agent as system service / daemon before login, and the user credentials gets active at user login time. Also should happen asl alternative mode with a popup as on windows client instead of manual editing the ~/.caa/caa.conf file. The .conf version is nice for commandline ilnuxes and servers. Desktop systems as Ubuntus, Mints etc. would prefer a simpler approach...
2. Same issue as on windows client, that obviously connection to Copernicus gets lost after a while which leads to unathenticated access to / via copernicus
Android and iOS Authentication
I really like those. See use cases for company use too, but actually it's nice for reporting and policy setting for the devices - especially on my kids tablets ;o)) Installation of the app via store is easy, and the certificate import also seems to work quite nice. Also here some isses / feedback:
1. Obviously the agent requires manual start, otherwise no authentication happens. This also should get installed as kind of background service automatically authenticating the client without need of manually open the app to get it start.
2. Same issue here, that authentication (connection ?) gets lost after a while and no automatic re-authentication happens. Leads to unauthenticated traffic to / via Copernicus
In General the possibilities all the clients offer are nice, however it seems, that the agents require some optimizations in view of:
- Running reliably on all systems as background service/daemon automatically authenticating on the firewall (without manual intervention after initial registration)
- Automatic re-authentication of the client, if connetion or auth on the firewall gets lost for some reason.
Every day new things to play around in copernicus...I'm in (technicians) heaven [:D]
Guest User!
You are not Sophos Staff.