英文:
How can I make my artifacts accessible to both organizational and non-organizational users?
问题
有一组织性的JFrog Artifactory，这意味着只有我的公司域内的用户可以访问这些工件。是否有办法使一个工件对组织内外的用户都可访问？
或者，是否可以将我的公司的JFrog Artifactory与另一个二进制仓库管理器同步？
我们正在开发一款面向内部和外部用户的应用程序，但外部用户无法访问这些工件，因为JFrog Artifactory受限于公司域。我们应该如何解决这个问题？
英文:
I have an organizational JFrog Artifactory, which means that only users within my company domain can access the artifacts. Is there any way to make one artifact accessible to both organizational and non-organizational users?
Alternatively, is it possible to synchronize my company's JFrog Artifactory with another binary repository manager?
We are building an application for both internal and external users, but external users are unable to access the artifacts because the JFrog Artifactory is restricted to the company domain. How can we overcome this?
答案1
得分: 1
Option1: 正如Louis所提到的，实现这个用例的最佳方法是拥有一个Edge节点（附带E+许可证），在该节点上，最终用户可以读取二进制文件。
Option2: 另一种选项是为Artifactory设置另一个域名。在高层次上，配置可以如下所示：
A. 对于内部用户，设置一个域名internal.abc.local -> 内部负载均衡器 -> 反向代理一个虚拟主机internal.abc.local -> <Artifactory作为后端服务器>;
B. 对于外部用户，设置一个独立的域名external.abc.com -> 外部负载均衡器（面向互联网）-> 反向代理到主机external.abc.come -> <Artifactory作为后端服务器>;
在上述示例中，我们可以使用一个反向代理来托管两个不同虚拟主机中的两个域名。
Option3: 另一种选择是选择一个可以通过互联网访问的JFrog SaaS服务器。您可以使用Artifactory的仓库复制将所需的构件从本地实例同步到SaaS实例。
英文:
Option1: As mentioned by Louis, the best way to achieve this use case is to have an Edge node (which comes with E+ licensing) where the end users can read the binaries.
Option2: is to have another domain name setup for the Artifactory. At a high level the configuration can look like this:
A. For internal users, have a domain internal.abc.local -> Internal load balancer -> Reverse proxy a virtual to host internal.abc.local -> <Artifactory as a backend server>
B. For external users, have a separate domain external.abc.com -> External load balancer (internet facing) -> Reverse proxy to host external.abc.come -> <Artifactory as a backend server>
In the above example, we can have one reverse proxy to host both domains in two different virtual hosts.
Option3: is to opt for a JFrog SaaS server that can be accessible over the internet. You can sync the required artifacts from the local instance to the SaaS instance using the Artifactory repository replication.
答案2
得分: 0
你可以使用具有智能仓库或发布包的边缘节点，并使你的边缘节点可以外部访问。
https://www.jfrog.com/confluence/display/JFROG/JFrog+Artifactory+Edge
https://www.jfrog.com/confluence/display/JFROG/Smart+Remote+Repositories
https://www.jfrog.com/confluence/display/JFROG/Distributing+Release+Bundles
英文:
You can use edge nodes with smart repositories or release bundles, and make your edge node externally accessible.
https://www.jfrog.com/confluence/display/JFROG/JFrog+Artifactory+Edge
https://www.jfrog.com/confluence/display/JFROG/Smart+Remote+Repositories
https://www.jfrog.com/confluence/display/JFROG/Distributing+Release+Bundles
答案3
得分: 0
JFrog许可不允许您与组织外的人分享构件。
即使是自托管的Artifactory Edge，也只能用于内部使用。
https://jfrog.com/self-hosted-terms-and-conditions/
Artifactory Edge Cloud在SaaS提供中没有此许可限制。该产品仅可用于外部共享构件。但仍然只能以只读模式共享：
> 允许除您的员工或服务提供商之外的任何个人或法人实体访问或使用Distribution Edges，但您可以授予第三方对每个Distribution Edge的仅下载访问权限；
https://jfrog.com/enterprise-distribution-edges-addendum/
英文:
JFrog license doesn't allow you to share artifacts with people outside of your organization.
Even self-hosted Artifactory Edge is only for internal usage.
https://jfrog.com/self-hosted-terms-and-conditions/
Artifactory Edge Cloud in SaaS offering doesn't have this license contraints. That product can only be used to share artifacts externally. Still you can only share in read-only mode:
> allow any person or legal entity other than your employees or service providers to access or use the Distribution Edges, except that you may grant third parties with download only access to each Distribution Edge;
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论