Vendor Accounts
How to get a NetID & DHE Account:
- Go to accounts.oit.duke.edu/ and log in
- Click on Request a new guest account for a non-Duke user under the Guest (Affiliate) Accounts section.
- Choose Consultant/3rd Party Support under Contractor (Non-clinical, No PHI Access)
- Under Select Guest Services select Duke NetID and Duke Medicine DHE Account
- Under Set Account Preferences, create a nickname (his is how it will show up when you view what accounts you have provisioned)
- Enter in the emails of the people you want to create a NetID/DHE account for
- Agree to the terms and click submit
- When the accounts are created you will be notified by email. Once they are created you may request a DHE Account.
How to Request a DHE Account (if they already have a NetID):
- Go to accounts.oit.duke.edu and log in
- Click on Request a new guest account for a non-Duke user under the Guest (Affiliate) Accounts section.
- Choose Consultant/3rd Party Support under Contractor (Non-clinical, No PHI Access)
- Under Select Guest Services select Duke NetID and Duke Medicine DHE Account
- Under Set Account Preferences, create a nickname (his is how it will show up when you view what accounts you have provisioned)
- Enter in the email associated with the person's existing NetID
- Agree to the terms and click submit
- When the accounts are created you will be notified by email. Once they are created you may request a DHE Account.
Duke Health Domain Access
How to Request DHE VPN Access
- Go to dhts.duke.edu
- Click Get IT
- Click Accounts & Access
- Click Account Access Order Guide - Maestro Care, Clinical & Business Applications and this should open a form.
- Requested For: The NetID you want to give DHE access to
- Approving Manager: Fill out who will sponsor this NetID gaining DHE access
- Type of Request: Probably Change
- Basic Services Options: Select VPN Access - Remote Access
- Click the Blue button in the top right to submit
How to Setup MFA (Multi-Factor Authentication)
MFA is required to access the DHE netwrok through VPN
- go to idms-mfa.oit.duke.edu and follow the prompts
How to Access Aegir (Drupal 7 sites Only)
Aegir is the system we use to deploy and manage our Drupal 7 websites. If you do not have access to Aegir, please contact Bernd Horn (bernd.horn@duke.edu) or Aaron Nelson (aaron.nelson@duke.edu) and we will create your account in Aegir.
How to Access GitLab
- Log into https://gitlab.dhe.duke.edu using your DHE account and password to generate your account in GitLab
- Notify Bernd Horn (bernd.horn@duke.edu) or Aaron Nelson (aaron.nelson@duke.edu) that you have logged in
- We will associate your account with the appropriate group and you will be able to view all of their git repos
Duke.edu and Vanity Domain Names
Third Level Domains i.e. something.duke.edu
Policies
- Third-level domains will be granted to Duke schools, departments, administrative units, interdisciplinary centers or institutes, and enterprise services.
- Third-level domain requests from entities that do not fall in the above categories will be reviewed on an individual basis, but will generally be denied.
- Third-level domains should clearly identify the requesting entity, avoiding the use of acronyms or generic terms that could apply to multiple campus entities or services.
- Requests for new third-level domains will be reviewed by the Associate Vice President for News and Communication, who will make the final decision on grating the domain.
- Third-level domains are a revocable resource. The revocation of a third-level domain will be a rare occurrence, but could happen, for example, if an existing third-level domain conflicts with the request of a major new University entity. Third-level domains may also be revoked if they have not been actively used for a period of one year. The review process for new third-level domains will include screening for current or potential future conflicts.
- Requests for a third-level domain name must originate from the IT director of the requesting entity, and have the endorsement of the entity's dean, director, or department head.
Process
- Petitioners for a third-level domain will submit their request via a web form (https://oit.duke.edu/about/policies/duke-domain-request-policy). The form will list the above policy for granting a third-level domain. Petitioners using any other means for their request (e.g. a call to the OIT or DHTS helpdesk, direct email, etc.) will be referred to the web form.
- Web requests are routed to Associate Vice President for News and Communication. The petitioner will receive an email acknowledging their request and an expected response time.
- The Associate Vice President for News and Communication will review the request and notify the OIT Domain Name Coordinator of the final decision.
- The OIT Domain Name Coordinator will notify the petitioner of the final decision.
- The petitioner may appeal the decision one time by forwarding their request, along with any relevant supporting information, to the OIT Domain Name Coordinator. The appeal will then be forwarded to a review committee consisting of the appropriate University senior officers.
- After the committee has considered the appeal and rendered a decision, the OIT Domain Name Coordinator will notify the petitioner of the decision via email.
Vanity Domains
Non duke.edu URLs, refered to as vanity domains. Examples are domain names that carry .org or .com extensions.
Policies
- Vanity domains must be approved by the governing entity of the requesting party i.e. Duke Health Marketing for DUHS sites and Director of Communications for the Office of the Dean for SOM sites.
- A site may have multiple vanity domains.
- All vanity domains should be purchased through DHTS using the SafeNames product. Contact aaron.nelson@duke.edu for more information.
- All vanity domains hosted with DHTS must be approved by the DHTS Information Security Office (ISO) prior to final approval.
Process
- Only .org extensions for Duke websites will be considered.
- Petitioners for a vanitydomain should include all proposed domain names in the New Web Site Request Form.
To have access to our systems vendors need a DHE account and DHE VPN access associated with that account (not just a NetID and regular VPN access).