Versions Compared

Old Version 16

changes.mady.by.user mhodges

Saved on

compared with

New Version 17

changes.mady.by.user mhodges

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Element Name

uhAcknowledgement

Description

Asserts for an individual the UH certifications and acknowledgements that have been obtained. For example, acknowledging online the UH General Confidentiality Notice
will result in an LDAP assertion that confirms that the individual has acknowledged the UH General Confidentiality notice.

Info
iconfalse
titleTip

An application developer can check for this assertion as a prerequisite for access to an application.
If the acknowledgement is missing, send the user to http://www.hawaii.edu/its/acer to perform the
acknowledgement. 


UH Data Classification

Restricted per Executive Policy 2.214

LDAP Attribute Info

  • Name: uhAcknowledgement
  • OID: 1.3.6.1.4.2160.1.1.2.10
  • Indexing: no
  • Required: no
  • Multivalued: yes

Required Format for Storage

string

Example Stored Data

  • generalConfidentialityNotice=20141231T000000
  • uhInformationSecurityAwarenessCertification=20140229T000000
  • uhHealthPlansEnrollmentOpportunity=20150515T000000
  • HawaiiEthicsCodeTrainingCert=20150515T000000
  • WorkplaceViolenceTrainingCert=20150515T000000
  • dmcaAccept=20150515T000000
  • dmcaReject=20150515T000000
  • uhSubstanceAbuseNoticeAcknowledgement=20150515T000000
  • creditCardInformationSecurityPolicy=20150515T000000
Systems of Record


Notes

  1. The date indicates when the acknowledgement or certification was most recently established.  The actual period of validity is not specified herein.
  2. For more information on GCN and ISAT values, please see <this blog post>.
  3. The data format is based on ISO 8601 and is stored in local time.
    1. The hour, minute, second portion may be defaulted to zeros or include the actual time. Subsequent experience with DateTime formats suggests that a canonical rather than a lexical DateTime data storage would have been more flexible and would also meet XML standards.
    2. For more information see http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ - (canonical form is yyyy-mm-ddThh:mm:ss).