• Drive Space low
  • Add more storage space (a SSD preferably) (can be done without service interruption if you are using a Logical Volume Manager)
• Out of RAM
  • Add more Memory
  • This warning is not yet supported for MSSQL or remote databases.
• Index Queue not empty
  • Can be ignored if intermittent small numbers
  • Contact support if large numbers persist
• HTTP pool too full
  • in multiserver.conf increase HTTP pools like Connection.CM_0.NumThreads to at least double the number of active users. (you may also have a CM_1 if you are using HTTP and HTTPS)
• DB pool full
  • The default setting of 30 in intranet.conf for DatabaseManager.DB.intranet.Connection.MaxPoolSize is already fairly high so normally this is an indication that the SQL server getting bogged down by slow spinning storage (LVMCache is recommended).
  • Increasing the number without ensuring the DB pool was filled because of volume (not latency) will likely cause out of memory or deadlock errors on the database instead of just slowness.

Overview

IWA allows for SSO using the Operating System users credentials.

Prerequisites

LDAP users have been successfully populated from AD; if not please refer to the AD Configuration Guide.

Quick reference

1. setspn -U -S HTTP/%noodle.domain.tld@DOMAIN.TLD %service_account
2. Add Noodle to "Microsoft Internet Explorer > Tools > Internet Options > Security > Local intranet > Sites > Advanced"
3. Use https://yourNoodle.tld/SPNEGO.po

Supported configurations

Browsers

Microsoft Internet Explorer, Mozilla Firefox, Google Chrome
Note: Microsoft Edge does not support this feature.

Protocols

Kerberos in SPNEGO in GSS-API (RFC 2478)
Note: NTLM, and NegoExts are not supported.

Endpoints

AD, Azure, and F5
Note: Others may work but have not been tested

Server configuration

Define the appropriate SPN for the account which Noodle is using to bind to LDAP.

• Within the AD Users and Groups snap-in Navigate to Noodle’s service (admin) account and set the follow attribute:
  1. servicePrincipalName = HTTP/%noodle_url
  2. Apply the change
• This may also be set via command line:
  1. setspn -U -S HTTP/%noodle.domain.tld@DOMAIN.TLD %service_account
• For Windows server 2008R2 or older command line instead use
  1. setspn -A HTTP/%noodle.domain.tld %service_account

Note:

• Logins from the AD Kerberos Server itself are not supported because Windows will attempt NTLM.
• For local installs, non-primary domains can be used with IWA by placing “IgnoreIWADomain = true” into intranet.conf 

Browser configuration

The next step in enabling IWA requires browser configurations to attempt authentication with the Noodle intranet website.

Once the configuration is in place users will need to access Noodle via the SPNEGO.po URL (ie. https://yourNoodle.tld/SPNEGO.po).

The following section of this guide explains this process.

Microsoft Internet Explorer & Google Chrome

Both of these browsers are configured with Microsoft Internet Explorer in "Tools > Internet Options > Security > Local intranet". 

Note:  If a non-default level is in use be sure “Automatic logon only in Intranet zone” is selected in "the Custom Level".

Next we will need to add the URL of your Noodle instance in "Sites > Advanced".

Mozilla Firefox

Enter “about:config” in the address bar, press “Enter”, and click “I Accept the Risk” when prompted.

Next, search for “auth.trusted”, enter your Noodle URL in the attribute entitled “network.negotiate-auth.trusted-uris” and select OK.

At this point IWA should be fully operational for your Noodle Intranet site!

If you manually installed PostgreSQL it should have the following done before Noodle connects to it

• permit password authentication via 127.0.0.1 in pg_hba.conf
• run init.sql

postgresql.conf ships with quite modest defaults so be sure to august it for anything more than light use. We recommend for ~4k users;

• Available Memory = System Memory - OS (1GB for Windows) - Java (100 to 512)
• effective_cache_size = Available Memory / 2
• shared_buffers  = effective_cache_size / 4
• max_locks_per_transaction = 512
• max_connections =  60
• checkpoint_segments 30
• log_min_duration_statement = 10000
• log_line_prefix =  ''%m: ''

There is a convenient config creator here.

The first encrypted request after starting Noodle can be 3 orders of magnitude slower than normal due to random entropy pool depletion. If your server suffers from this issue (most EC2 servers) you can verify by checking the pool size:

cd /proc/sys/kernel/random/ && cat poolsize entropy_avail

There are at least 3 solutions to a depleted pool:

1 Hardware

Some hardware includes random generators (like the rdrand CPU flag):

cat /proc/cpuinfo | grep -ic rdrand

You can enable its use with:

Debian/Ubuntu

apt install rng-tools
systemctl start rng-tools.service
systemctl enable rng-tools.service

Fedora/RedHat

yum install rng-tools
systemctl start rngd.service
systemctl enable rngd.service

2 urandom

If you don't have a hardware generator or you don't trust it you can edit /opt/Noodle/multiserver to use:

-Djava.security.egd=file:///dev/urandom

Or edit java.security in $JRE8/lib/security or $JRE9/conf/security to use:

securerandom.source=file:/dev/urandom

3 haveged

For higher throughput and lower CPU usage than urandom haveged can be used but it can still block:

Debian/Ubuntu

apt install haveged
systemctl start haveged.service
systemctl enable haveged.service

Fedora/RedHat

yum install haveged
systemctl start haveged.service
systemctl enable haveged.service

keytool -storepass 123 -keystore noodle.jks -importcert -file server.crt -alias domain.tld

server.crt can be a pem or der file. Make sure root and intermediate certificates are included for a complete chain.

Official keytool manual

Official openssl manual