[jira] [Assigned] (MESOS-3096) Authentication for Communicating with Docker Registry
[ https://issues.apache.org/jira/browse/MESOS-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jojy Varghese reassigned MESOS-3096: Assignee: Jojy Varghese (was: Lily Chen) > Authentication for Communicating with Docker Registry > - > > Key: MESOS-3096 > URL: https://issues.apache.org/jira/browse/MESOS-3096 > Project: Mesos > Issue Type: Improvement >Reporter: Lily Chen >Assignee: Jojy Varghese > Labels: mesosphere > > In order to pull Docker images from Docker Hub and private Docker registries, > the provisioner must support two primary authentication frameworks to > authenticate with the registries, basic authentication and the OAuth2.0 > authorization framework, as per the docker registry spec. A Docker registry > can also operate in standalone mode and may not require authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3096) Authentication for Communicating with Docker Registry
[ https://issues.apache.org/jira/browse/MESOS-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lily Chen reassigned MESOS-3096: Assignee: Lily Chen Authentication for Communicating with Docker Registry - Key: MESOS-3096 URL: https://issues.apache.org/jira/browse/MESOS-3096 Project: Mesos Issue Type: Improvement Reporter: Lily Chen Assignee: Lily Chen Labels: mesosphere In order to pull Docker images from Docker Hub and private Docker registries, the provisioner must support two primary authentication frameworks to authenticate with the registries, basic authentication and the OAuth2.0 authorization framework, as per the docker registry spec. A Docker registry can also operate in standalone mode and may not require authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
