[RTFACT-14848] Message not correct in Set Me Up of virtuals repositories Created: 25/Aug/17  Updated: 11/Feb/20  Resolved: 11/Feb/20

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Virtual Repositories
Affects Version/s: 5.4.5, 5.4.6, 5.5.1
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Jean-Claude Douine Assignee: Inbar Tal
Resolution: Fixed Votes: 10
Labels: None
Environment:

Linux centos OS on VMs in openstack infrastructure.


Issue Links:
Duplicate
is duplicated by RTFACT-18455 "Set Me Up" claims I do not have perm... Open
is duplicated by RTFACT-16195 User with permissions is getting UI a... Resolved
Assigned QA: Ido Klotz

 Description   

A user have the rights OK to write in a local repository to push artifacts ; Set Me Up is OK when the end user click on Set Me Up.
We use virtual repositories containing the effective local repository and other remote or locals repositories ( mirror of distant repository on replication push infrastructure for example ). And all clients know only this virtual repository ( their never delete artifacts ). The problem is that in Set Me Up of the virtual repository , the client read this info "! You do not have deploy permissions to this repository " This info is not correct because they can really push in virtual which will write in local repository .
It would be good to suppress this "not correct" message in virtual repositories



 Comments   
Comment by Krzysztof Malinowski [ 26/Feb/18 ]

I confirm this behavior on 5.3.2 as well.

Comment by Waldek Maleska [ 26/Feb/18 ]

This a remain of partial solution of https://www.jfrog.com/jira/browse/RTFACT-14334 where no Set Up instruction was presented at all.

5.6.2 version provides the appropriate URLs but still shows the warning.

I've checked on 5.8.3 and the warning is gone; what's strange however is that it's gone even in situation where my user account actually can't (doesn't have the rights set up) to deploy the files into the target repository. This seems somewhat sub-optimal.

Comment by Ehud Hoggeg [ 17/Dec/18 ]

Happens on Artifactory Enterprise 6.0.3 rev 60003900, pretty disturbing

Comment by Jeff Blaine [ 02/Apr/19 ]

Still presenting misleading info in 6.5.15

Generated at Tue Feb 18 08:12:22 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.