The Incommon Federation wiki has moved.

Please visit the new InCommon Federation Library wiki for updated content. Remember to update your bookmarks.

Click in the link above if you are not automatically redirected in 15 seconds.



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Application Form for the R&S Category

To have your service considered for the Research & Scholarship (R&S) Category, a principal investigator, site administrator, technical contact, or some other responsible individual should complete and submit this web form. All fields are required.

Questions? Please send email to admin@incommon.org with "R&S Application" in the subject line.

Unknown macro: {mail-form}
Unknown macro: {mail-input}
Unknown macro: {mail-input}

Service Information

Name of my service (i.e., the DisplayName in metadata):

Unknown macro: {mail-input}

Name of the organization that owns/runs my service (i.e., the OrganizationName in metadata):

Unknown macro: {mail-input}

The entityID of my service (to determine your entityID, browse the entity info pages):

Unknown macro: {mail-input}

Information URL of my service (i.e., the InformationURL in metadata, for end users):

Unknown macro: {mail-input}

Login URL of my service:

Unknown macro: {mail-input}

How my service supports research and scholarship (2–3 sentences):

Unknown macro: {mail-textarea}

Requirements

Unknown macro: {mail-input}

I have read the Research & Scholarship Entity Category specification and hereby declare that my service satisfies the requirements of this specification.

My service meets the following basic requirements:

Unknown macro: {mail-input}

My service is operated for the purposes of supporting research and scholarship interaction, collaboration or management, at least in part.

Unknown macro: {mail-input}

My service metadata has been submitted to InCommon and has been published in InCommon's public metadata aggregate.

Unknown macro: {mail-input}

My service refreshes and verifies metadata at least daily.

My service meets the following technical requirements:

Unknown macro: {mail-input}

My service is a production SAML deployment that supports the SAML V2.0 HTTP-POST binding.

Unknown macro: {mail-input}

My service provides both an [MDUI DisplayName] and an [MDUI InformationURL] in metadata.

Unknown macro: {mail-input}

My service provides both technical and administrative contacts in metadata.

Unknown macro: {mail-input}

My service provides requested attributes in metadata.

My service meets the following privacy requirements:

Unknown macro: {mail-input}

 Yes 

Unknown macro: {mail-input}

 No This field is required. Are the requested attributes in metadata a subset of the R&S attribute bundle? (Note: This is highly RECOMMENDED otherwise a bilateral agreement with each IdP may be required.)

Unknown macro: {mail-input}

My service requests only those attributes required to operate the service.

Unknown macro: {mail-input}

My service will not use attributes for purposes that fall outside of the service definition.

Unknown macro: {mail-input}

I have read the InCommon Participation Agreement and understand that my service is bound by this Agreement (which was signed by my parent organization) and therefore my service is subject to the Privacy constraints outlined in section 9 of that document.

Personal Information

Unknown macro: {mail-input}
Unknown macro: {mail-input}

My name:

Unknown macro: {mail-input}

My email address:

Unknown macro: {mail-input}

My affiliation with this service (PI, site administrator, technical contact, service operator, etc.):

Unknown macro: {mail-input}

Unknown macro: {mail-input}

By pressing the "Submit Application" button, I certify that all of the above statements are true and correct to the best of my knowledge.

Unknown macro: {mail-submit}
Unknown macro: {mail-success}

Application Accepted!

Thank you for applying for R&S. Someone will contact you asap.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels