Description of problem: This BZ tracks effort of rebasing gswauth to latest swauth code that has many fixes. This rebase effort is limited to back-porting relevant fixes to gswauth. Backports on review: http://review.gluster.org/#/q/project:gluster-swift+branch:master+topic:rebase-gswauth
There's a series of five upstream changes on review: http://review.gluster.org/#/q/project:gluster-swift+branch:master+topic:rebase-gswauth
Upstream changes: http://review.gluster.org/#/q/project:gluster-swift+topic:rebase-gswauth Downstream changes: https://code.engineering.redhat.com/gerrit/#/q/project:swiftonfile+branch:rhgs-3.1.3+topic:bug/1314172
To verify this backport, took the latest build of swiftonfile with glusterfs latest build and executed the full regression suite for temp auth and gswauth , I see no failures or issues with the existing tests. If in further testing find any issue with gswauth, will be raising another BZ. Marking the BZ verified. swiftonfile-2.3.0-2.el7rhgs.noarch glusterfs-3.7.9-1.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1289