Last updated at 2022-08-11 09:34:25 by ouit0354
Differences between revisions 1 and 15 (spanning 14 versions)
Revision 1 as of 2017-01-12 09:19:55
Size: 1345
Editor: ouit0354
Comment:
Revision 15 as of 2018-07-23 12:21:42
Size: 4415
Editor: ouit0354
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= University of Oxford Apple Developer Account =
The University has an Apple Developer Account which units may use to sign and release their iOS and macOS applications to the relevant App Stores.
## page was renamed from Developer
## page was renamed from ADP
## page was renamed from Apple Developer Programs
## page was renamed from ITSS/AppleDev
= University of Oxford Apple Developer Programs =
The University has accounts with two Apple Developer Programs:
 * A normal Apple Developer Program account which units may use to sign and release their iOS and macOS applications to the relevant App Stores (see https://developer.apple.com/programs/)
 * An Apple Developer Enterprise Program account, for signing and distributing 'in-house' applications (see https://developer.apple.com/programs/enterprise/)
Line 5: Line 11:
NSMS purchased a Developer Account with a signing identity for the University of Oxford when they became available several years ago. Apple only allow one identity per [[https://en.wikipedia.org/wiki/Data_Universal_Numbering_System|D-U-N-S number]] so we have kept the management of this account, and provide a best efforts service in administering it. Please note that since we do not receive compensation for our time it is not a formal service with an SLA. The NSMS team within IT Services purchased Developer Accounts with a signing identities for the University of Oxford when they became available several years ago. Apple only allow one developer/enterprise developer identity per [[https://en.wikipedia.org/wiki/Data_Universal_Numbering_System|D-U-N-S number]], and the University only has one number, so we have kept the management of these accounts and provide a best efforts service in administering it. Please note that since we do not receive compensation for our time it is not a formal service with an SLA. It is now under the management of the Orchard team within EDMS (Endpoint Device Management Services).
Line 8: Line 14:
=== Mailing List ===
There is a mailing list, apple-app-developers@maillist.ox.ac.uk which all members of the Apple Developer accounts should be signed up to. This is where any discussion about the Developer Account should take place.
Line 9: Line 17:
For detailed information on what each level of membership entails, please see [[https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/ManagingYourTeam/ManagingYourTeam.html|Apple's documentation]]. In summary:
Line 10: Line 19:
There is only one agent account, and this is managed by NSMS. This is the account that will
=== Admins ===
Each unit that wishes to use the Developer Account should nominate one person to be their developer admin. This person will have admin permissions on the Developer Account portal. The admin can change the app id of an application, and also sign them for distribution. Admins can also add new members, but we ask that they do not grant alter membership levels for any other person in the team.
=== Members ===
Members can create development certificates and register devices to develop on
There is only one agent account, and this is managed by IT Services (EDMS). This is the account that can accept legal terms, create developer ID certificates and renew the account.
==== Admins ====
Each unit that wishes to use the Developer Account should nominate one person to be their developer admin. This person will have admin permissions on the Developer Program account portal. The admin can change the app id of an application, and also sign them for distribution. Admins can also add new members, but we ask that they do not grant or alter membership levels for any other person in the team.
==== Members ====
Members can create development certificates and register devices to develop on. Please note that we suggest that you stick to '''a maximum of 5 development devices'''. This is because there is a maximum of 100 total for the entire University.
=== iTunes Connect ===
iTunes Connect allows developers to submit and release their apps on the relevant App Stores, and allows agents to transfer in apps from other Developer IDs. It has its own set of membership permissions which we are currently assessing, currently users can request the access they need on the mailing list.

== Certificates ==
By becoming part of the University's Developer Program, you agree to maintain the security of any certificates involved and their private signing keys. Please alert the mailing list '''immediately''' if you believe any of the following have happened:
 * The main iOS or macOS distribution certificates have been revoked or deleted (this will affect everyone in the program)
 * A certificate or private key has been compromised or lost
 * Someone who is not a member of the program is signing apps with our certificate
 * You have any other concern about a certificate or security issue not listed
'''Do ''not'' attach certificates or private keys to emails to the mailing list.'''

== Requesting Access ==
Requests for access should be done formally by someone with high level administrative responsibility for a department/research group etc. They should email orchard@it.ox.ac.uk with the request, which should include:
 * Your nominated Developer Program admin user's name and email address (probably the technical lead)
 * Your required member users names and email addresses (the other developers)
 * Please include the line "I agree to the terms laid out on https://docs.orchard.ox.ac.uk/DeveloperPrograms"
We will set up your access to the account/mailing list as soon as possible and inform you when this is done.

University of Oxford Apple Developer Programs

The University has accounts with two Apple Developer Programs:

History

The NSMS team within IT Services purchased Developer Accounts with a signing identities for the University of Oxford when they became available several years ago. Apple only allow one developer/enterprise developer identity per D-U-N-S number, and the University only has one number, so we have kept the management of these accounts and provide a best efforts service in administering it. Please note that since we do not receive compensation for our time it is not a formal service with an SLA. It is now under the management of the Orchard team within EDMS (Endpoint Device Management Services).

General Information

Mailing List

There is a mailing list, apple-app-developers@maillist.ox.ac.uk which all members of the Apple Developer accounts should be signed up to. This is where any discussion about the Developer Account should take place.

Team Levels

For detailed information on what each level of membership entails, please see Apple's documentation. In summary:

Agent

There is only one agent account, and this is managed by IT Services (EDMS). This is the account that can accept legal terms, create developer ID certificates and renew the account.

Admins

Each unit that wishes to use the Developer Account should nominate one person to be their developer admin. This person will have admin permissions on the Developer Program account portal. The admin can change the app id of an application, and also sign them for distribution. Admins can also add new members, but we ask that they do not grant or alter membership levels for any other person in the team.

Members

Members can create development certificates and register devices to develop on. Please note that we suggest that you stick to a maximum of 5 development devices. This is because there is a maximum of 100 total for the entire University.

iTunes Connect

iTunes Connect allows developers to submit and release their apps on the relevant App Stores, and allows agents to transfer in apps from other Developer IDs. It has its own set of membership permissions which we are currently assessing, currently users can request the access they need on the mailing list.

Certificates

By becoming part of the University's Developer Program, you agree to maintain the security of any certificates involved and their private signing keys. Please alert the mailing list immediately if you believe any of the following have happened:

  • The main iOS or macOS distribution certificates have been revoked or deleted (this will affect everyone in the program)
  • A certificate or private key has been compromised or lost
  • Someone who is not a member of the program is signing apps with our certificate
  • You have any other concern about a certificate or security issue not listed

Do not attach certificates or private keys to emails to the mailing list.

Requesting Access

Requests for access should be done formally by someone with high level administrative responsibility for a department/research group etc. They should email orchard@it.ox.ac.uk with the request, which should include:

  • Your nominated Developer Program admin user's name and email address (probably the technical lead)
  • Your required member users names and email addresses (the other developers)
  • Please include the line "I agree to the terms laid out on https://docs.orchard.ox.ac.uk/DeveloperPrograms"

We will set up your access to the account/mailing list as soon as possible and inform you when this is done.


Orchard is a close co-operation of