• Created by user-b937b, last updated on Jan 18, 2008 1 minute read

ApplicantID Activation Web App

  • An end user can activate their ApplicantID using a previously supplied activation code
  • Sets password in NetID Kerberos KDC
  • Sets security questions for ApplicantID Forgot Password web app
  • Custom web app created at CIT
  • New password must meet complexity rules
  • Uses Java and Spring framework
  • Uses Tomcat (shared instance with several other IdM web apps)
  • Uses Apache web server
  • Uses SSL
  • Uses kadmin C binary to hit Guest Kerberos KDC via Kerberos 5
  • Uses JDBC with ID/password for Oracle DB which stores security questions
    • Oracle DB is hosted by DBA group. IdM has our own DB instance on shared hardware
    • Security questions are encrypted by app with Java Cryptography Extension PBEWithSHA1AndDESede
  • Activation code currently stored in Directory Server
    • Uses LDAP and SSL with BindID/password
    • Will get stored in Oracle instead of Directory Server soon
  • OS: Solaris 5.9 Cluster
  • No automatic fail over
    • But can be moved manually via scswitch commands
  • No load balancing
  • Machines are in server farm
    • Two factor AuthN required for SSH login
  • Production: 3 node cluster
    • Shares node with some other IdM web apps
  • Test: 2 node cluster
  • Dev: 2 node cluster
  • No labels