Noodle can integrate with Large Language Models to aid in content creation. ArtificialAnalysis.ai has a nice pricing, quality, and speed overview. One token is roughly equivalent to 0.75 million words.

Links to 3rd party Application Programming Interfaces and pricing:

Free tiers:

• x.ai ($25/month free + $7.50 / 1M Tokens)
• google.com (Gemini 1.5 Flash: 1.5k requests / day + $0.13 / 1M Tokens)
• huggingface.co (1k requests / day + $9 / month for 20k requests / day)

Paid only:

• anthropic.com (Haiku: $2 / 2M Tokens)
• openai.com (o1-mini: $5.25 / 1M tokens)

Wikipedia has a list. Comments on the popular options;

• Apache - Tomcat (most popular)
• Eclipse - Jetty (small and fast)
• Eclipse - GlassFish (heavy)
• Payara - Payara
• Red Hat - WildFly / JBoss EAP

Micro services; fast start with native executables via GraalVM;

• Red Hat - Quarkus
• Micronaut - Micronauts

Specifications at jakarta.

Long Term Support versions (annually)

Release versions (monthly)

Overview

SAML allows for SSO using the Web Browser users credentials.

Noodle Prerequisites

If AD is being used, LDAP users should have already been populated within Noodle.

Quick reference

1. Save your IdP URL and fingerprint in your SP (Noodle)
2. Use https://yourNoodle.tld/SAML.po in your IdP settings and Web Browser.

Supported IdPs

Onelogin, Okta, and Azure
Note: Contact us for assistance integrating Other IdPs.

Noodle Configuration

In Noodle navigate to “System Tools > Settings > Single Sign-On”

Both URL & fingerprint will be supplied by your IdP vendor. Your IdP may provide an XML file which contains the URL and certificate, to convert the certificate into a SHA-1 fingerprint there are some online SAML tools:

Format Certificate

Calculate Fingerprint

IdP Configuration

Your IdP will require a location to direct SAML responses, use https://yourNoodle.tld/SAML.po.  Noodle will be compatible with the default settings of most IdPs.

OneLogin

1. Navigate to "Administration > Applications > Add App"
2. Search for "SAML Test Connector (IdP)"
3. setting tabs
   • Info (all optional)
   • Configuration
     • ACS (Consumer) URL Validator = .*
     • ACS (Consumer) URL = https://yourNoodle.tld/SAML.po
     • the rest can be left blank
   • Parameters
     • Configured by admin
       • NameID (fka Email) = Email
   • Rules (all optional)
   • SSO
     • X.509 Certificate = 2048-bit
       • View details will show the fingerprint
     • SAML Signature Algorithm = SHA-1
     • SAML 2.0 Endpoint (HTTP)
       • This is the URL to save in Noodle
   • Access (all optional)
   • Users (make sure you add some)
   • Privileges (all optional)

Azure

1. Azure Active Directory > Enterprise applications > New Application
2. Non-gallery Application > Name can be anything > 2 Single sign on > SAML
   • set "Identifier (Entity ID)" to the domain name for the Noodle instance
   • set the "Reply URL" to https://yourNoodle.tld/SAML.po
   • copy the "Thumbprint" and "Login URL" to put in the Noodle settings

• Average number of logins per day
• Application usage
• Number of Logins per user
• Index Queue
• Error Codes
• User Activity
• Page Hits
• Item Views
• User IPs
• User Time
• Storage Space Occupied
• Shared Folders
• Large Files
• Home Folders

Some intermediate servers (proxy/gateway/firewall/router/etc) will answer a request from the browser on behalf of the server. If this happens frequently and you are unable to change the intermediate server to avoid this (supporting 2 minute connections is a good start) you can use

top.noodle.ajax.ignoreMasquerading=true;

use that as a last resort as it can cause further UI interference.