Release Summary

This minor release includes general changes that have little impact on college users. The following are the main changes:

• Conductor Upgrade 

  Exposed internal communication endpoints through

  CCCApply application delivery to colleges via the college adaptor will now be handled by a new conductor instance.

  • To support this new system, a new API Gateway has also been implemented using Tyk. 

  • The new Tyk

  was implemented in addition to

  • API gateway is implemented alongside the service router; this allows testing in parallel.

• Changes were made to use Postgres in addition to ES/EC. The new system will be on Postgres to run in parallel.

• Updated the bi-directional fraud reporting API.

• Updated KeyCloak.

• • The new conductor instance makes use of a Postgres database, while the existing conductor instance continues to use ElasticSearch/ElastiCache (ES/EC) for persistence.

  • To support this new system, for each college adaptor worker, several new clients have been created in Keycloak.

• Updated the SuperGlue Fraud Reporting API.

  • Superglue Fraud Reporting has been integrated with the CCC Apply SPAM Filter. With this change fraud identified through the SPAM Filter or fraud reports submitted to Enabling Services will be made available through the Superglue Fraud Reporting workflow to alert colleges of possible fraudulent applications.

  • Fraud reports submitted through the Superglue Fraud API will mark that application as confirmed fraud in the CCC Apply database

Documentation

Existing documentation, SuperGlue Bi-Directional Fraud Data API Reporting Guide, details the bi directional fraud report Bi-directional Fraud Reporting functionality. This guide will be updated to include new, moderate changes in this release.In addition, this change to the bi-directional fraud reporting API is described in Jira ticket PLATFORM-2218details on the impacts to using the API.