Category:I805 Authentication and Authorization

From ICO wiki
Revision as of 19:04, 20 February 2017 by Lvosandi (talk | contribs) (Biznisplan)

Authentication and Authorization

General information

In this course we continue where we left off with Firewalls and VPN/IPsec course.

Relevant topics for research and implementation in the lab. Lectures coming up for most of the topics:

  • File based password stores eg. /etc/shadow, .htaccess
  • Signing and encrypting e-mail using GPG
  • Active Directory protocols: LM, NTLM, Kerberos, GSSAPI, SPNEGO, LDAP
  • More TLS and client side authentication in particular
  • Filesystem permissions: access control lists, selinux, apparmor
  • Multi-factor authentication: smartcards, Yubikey, Mobile-ID, etc
  • Contactless cards
  • On the web: Cookies, OAuth, OpenID, iPizza,

Intro slides & video recording:


  • 3pcs Sun server in the college server room
  • TP-Link WDR3600 wireless router routed to 172.16.*.*
  • HP Probook dual-boot laptop
  • iMac in 412, use admin/admin to log in with local account
  • Robotics Club (wireless) network, routed to to 172.16.*.*

If you forget (local) Windows password use System Rescue CD to reset the password:


Every service should use accounts from Active Directory. To achieve that try to use LDAP protocol first. Via LDAP you can retreieve the data about accounts. If the service machine is not joined to domain create a service account in AD to access LDAP interface first. It really depends on the software how you need to configure it.

For fileserver/SSH/FTP/mail server first join to domain using winbind: For NextCloud,, OwnCloud and most web services configure LDAP plugin to retrieve accounts from AD and LDAP bind authentication.


Everybody should have a task, prepare a howto on the college wiki and have a topic for presentation:

  • Mohanad - AD up and running, routing, howto for setting up Active Directory on Windows Server, creating accounts and groups
  • Etienne - NextCloud server set up, howto for configuring client/app
  • Taavi - Wiki accounts from AD, possibly using Kerberos SSO
  • Madis Lugus - Gogs accounts from AD, possibly using Kerberos SSO and also SSH public keys from AD
  • Joosep - clone, web server and MySQL with accoutns from AD
  • Meelis - with accounts from AD via LDAP, possibly with Kerberos SSO, howto for configuring apps
  • Sheela - mailserver with accounts from AD via LDAP, with GSSAPI authentication, howto for configuring Thunderbird/Evolution
  • Ardi - OpenVPN with ID-card auth, isikukood from AD attribute, howto for configuring client
  • Marvin - secondary AD, routing, <insert topic of your interest>
  • Arti - Samba as third DC, <insert topic of your interest>
  • Kustas - pentest
  • Ender - pentest
  • Mikus - pentest
  • Artur - how are you going to pass the course?
  • Keijo - how are you going to pass the course?
  • Anton - how are you going to pass the course?
  • Tarvo - how are you going to pass the course?
  • Ats - how are you going to pass the course?
  • Nazmul - how are you going to pass the course?


Presentation of up to 30min should cover what you did in order to get the service running in the desired state, what problems you had, how others can use your service and what can be done to improve the setup.

This should be more or less in logical order:

  • 7. mar - Mohanad, Etienne
  • 14. mar - Taavi, Madis
  • 21. mar - Joosep, Meelis
  • 5. apr - Sheela, Ardi
  • 12. apr - backup slot
  • 19. apr - Marvin, Arti
  • 26. apr - Kustas & Ender


This is just to keep activities in sync

Milestone 1

Domain controller is working. In the internal network and over VPN connection DNS requests work as expected.

On a Linux box command line users can authenticate with kerberos client utils:

 kinit username@OFFICE.LAN

On a Linux box command line users can fetch stuff via LDAP:

ldapsearch -b dc=office,dc=lan  -H ldap:// -D lauri@office.lan -W

Also authenitcation with Kerberos should work:

ldapsearch -b dc=office,dc=lan  -H ldap:// -Y GSSAPI

To make life easier configure /etc/ldap/ldap.conf, if properly configured short commands work:


Milestone 2

Deadline 21. Feb

Following services are using credentials from AD

  • NextCloud - Etienne
  • - Meelis
  • nagios - Mohanad
  • wiki - Taavi
  • mailserver - Sheela

Milestone 3

Deadline 28. Feb

Service owner has client application configured and knows how to configure them:

  • NextCloud - app on smartphone, SPNEGO with web browser
  • - app on smartphone, SPNEGO with web browser
  • nagios - SPNEGO with web browser
  • wiki - SPNEGO with web browser
  • mailserver - Evolution or Thunderbird with SMTP/IMAP+GSSAPI

Milestone 4

Deadline 7. Feb

Manual page created on internal wiki for configuring the client application(s). Other students are using your service.

Milestone 5

Keep services up and running, respond to incidents until 5th of June. Server teardown on 5th of May. Wipe harddisks.

Pages in category "I805 Authentication and Authorization"

This category contains only the following page.