I too would also like an answer to this question. We've recently update our RSA Authentication Manager to 8.2 SP1. Is there a future release or workaround to use SMBv2+ to do backups?
No news from RSA
Contractor to the Office of the Chief Information Officer
U.S. Department of Energy
National Nuclear Security Administration
NNSA Albuquerque Complex, PO Box 5400
Albuquerque, NM 87185-5400
Classified Email: firstname.lastname@example.org<mailto:email@example.com>
As everyone has discovered, the Authentication Manager ver. 8.2 SP1 appliance does not support communications (archive logs or backups) with a remote Windows File Share that uses SMBv2 or v3. Only SMBv1 will work.
This situation will not change with the introduction of AM 8.3 scheduled for this coming January. AM 8.2 and 8.3 use Suse Linux 11 SP4 as their operating system, and Suse Linux 11 SP4 only supports SMBv1. Suse has informed RSA that there are no plans to add SMBv2 or later support to Suse 11 SP4, and that customers would need to upgrade to Suse Linux 12 for support for anything greater than SMBv1. RSA Engineering is aggressively pressing Suse for a solution to this problem short of the forklift OS upgrade to Suse Linux 12, but there is no timeline on this yet. Only work-arounds are to backup to NFS or locally.
unfortunately no, Suse still refuses to provide fix for Suse 11 to support SMBv2, which means RSA has to plan for a forklift upgrade to the AM appliance from Suse 11 to Suse 12 in order to be able to provide SMBv2 support for remote backups and syslogs
Any updates on this? Do you have more info on when SMBv2 might be supported? When would RSA switch their appliance to Suse 12?