| Feature | Summary |
| Site Architecture > Search Page Designer - deleting a page fully removes its Uploads exception on allow-list sites | On a site whose web.config serves only listed file types, deleting a search page now removes that page's whole Uploads exception from web.config.
- No
.aspx allow entry is left behind for the deleted page.
- Sites that do not use an allow-list are not affected.
|
| Site-wide - two unused Kaiser.xlsx sample files are removed from each Master | The Master no longer keeps the sample workbook Kaiser.xlsx in Uploads/Files and Uploads/Uploads/Files.
- The update deletes each copy only when it still matches the shipped file. A file you changed is kept.
- Nothing in Centralpoint reads these files.
|
| Master > Development > Utilities - the custom Bin comparison page under Uploads is removed (web.config change) | The developer page Uploads/Utilities/Utility.aspx, which compared Bin folders, is removed from each Master, along with its web.config exception.
- The update deletes
Utility.aspx, Utility.aspx.cs and Original Sync Exclusions.txt when they still match the shipped files. A file you changed is kept.
- No page under the Master's
Uploads folder runs any more. A changed copy of Utility.aspx left on a Master returns 404.
web.config change. The update removes this block from the Master Root\Web.config only. Site web.config files are not touched. A copy of the file is saved to Backups\RemoveUtilityPageUploadsException.Web.Config first.
<location path="Uploads/Utilities/Utility.aspx">
<system.webServer><security><requestFiltering><fileExtensions>
<remove fileExtension=".aspx" />
</fileExtensions></requestFiltering></security></system.webServer>
</location>
- A virtual directory that runs as its own IIS application keeps its own
web.config, which the update does not change. Remove the same block there if it has one.
- Custom code or a bookmark that opened
Utility.aspx now gets a 404.
|
| Master > Services web service - the My Updates package methods are removed, and its WSDL is no longer published | The Master's Services web service (/WebServices/Services.svc) no longer offers the My Updates package methods.
MyUpdatesBuildPackage and MyUpdatesInstallPackage are removed. A script that calls either one now gets an error.
- The service no longer publishes its description (WSDL), so a new client cannot be generated from the live service.
DataTransferExecute and Test work as before with a Service Key from Tools > Serivice Key.
- The update replaces
WebServices/Web.config on the Master. Any local edit to that file must be applied again.
|
| Site-wide - content tree, restore version, file password and click tracking errors no longer show server details | When a request behind one of these CpScripts fails, the page now gets the message "Error" instead of server error details such as code paths.
DocumentShellTree and MediaElementsTree CpScripts: a failed tree update shows "Error" in the editor.
RestoreVersion CpScript and the Policies and Procedures version list: a failed restore returns no error details. A successful restore works as before.
FileOutputAuthenticate CpScript: a failed password check still shows "Authentication failed."
ModuleSearchAccordionMenu CpScript: a failed click tracking request returns no error details.
|
| Master > Development > Health Monitor - the export files are always written to the Master's own Uploads folder | The two Generate File buttons on Master > Development > Health Monitor now always write their file to the Master's own Uploads folder.
- The Health Monitor Data export and the xQuery In Data Sources file download from the same links as before.
- A request can no longer send either file to a different folder or network share.
|
| Site-wide - a Master or Uber sign-in to the Console ends within a minute of that account being locked or deleted | A Master or Uber administrator signed in to your Console now loses access within about a minute when their own account is locked or deleted.
- This applies to every Console page and action, not only new sign-ins.
- Accounts on your own site are not affected.
- If the Master or Uber cannot be reached during the check, a session that was already valid keeps working and is checked again a minute later.
|
| Site-wide - saving a server's signing state retries when another program holds the file | Saving a server's signing state, and promoting its next signing key, now retries when another program such as an antivirus scanner briefly holds the file. Each save uses its own temporary file, and leftover temporary files are cleaned up.
- This applies to the site's API and to the Centralpoint CLI 8.12.17.7 signing key commands.
- The Centralpoint Agent moves to 8.12.17.6 with the same shared code.
|
| Broadcasts > Broadcasts - a member missing from the Users in DataCurrent list gets empty data, not an error message | In a broadcast whose data source uses Users in DataCurrent, a member with no matching row now gets the data source's empty content. Before, the error text could appear in that member's message.
|
| Data Transform > Data Transfer - an MD-Staff source with no rows shows an empty preview | An MD-Staff source that returns no rows now shows an empty preview with its columns in Data Transform > Data Transfer, instead of an error. A transfer run from an empty source behaves as before.
|
| Master > Deployment > Web Sites - turning a site's Console on or off no longer fails when IIS already matches | Turning a site's Console on or off from its page in Master > Deployment > Web Sites no longer fails when IIS already has the Console in the requested state. This happens when the database and IIS disagree, for example after a manual IIS change.
|
| Master > Content > Scheduled Tasks - a lost database connection reading advanced tasks groups with connection errors | When the Master cannot reach its database while reading the advanced scheduled tasks, the error is now recorded as a database connection error. It groups with the other connection errors instead of as a separate scheduled task error, so one outage shows as one entry.
|
| Master > Content > Scheduled Tasks > DataUpdate - Uploads files deleted at the source mid-copy are counted, not skipped | When a file is deleted from the source Uploads folder while DataUpdate is copying it, the run no longer reports it as a skipped file or marks the run as having errors. The process log shows how many files were removed at the source. A file that cannot be copied for any other reason, or a source folder that disappears, is still reported as skipped.
|
| Development > Errors - a relation population that overflows a column type gets its own repair note | When populating a relation fails because a value is too large for its type, such as 1000 in a tinyint column, the error now carries a note on what to check. It asks you to compare the value with the attribute's configured type and the relation column, correct the value or widen the type, and then run Development > Utilities > Populate Relation for the module.
|
| Site Architecture > Module Designer - a request that ends early is no longer reported as a module view error | When a request ends while a page is loading a module view user control, such as a redirect or a timeout, it is no longer recorded as a failure of that module view in Development > Errors. A user control that really fails to load is still reported with the module view name, as before.
|
| AI Governance > AI Indexing - indexing waits for its database tables, and the banner says when they are missing | On SQL Server 2022 or later, vector indexing now waits until its database tables exist, and the pages say so instead of asking for a SQL Server upgrade.
AI Governance > AI Indexing, AI Governance > Knowledge Assistant and the AI Providers page show "The vector tables are not installed on this database yet", with how they get created.
- Background indexing no longer reports errors while the tables are missing, and starts on its own once a sync creates them.
- The availability check is repeated every few minutes until the tables exist, so no restart is needed.
|
| Development > Web API - GetUser returns a 404 for a missing user, and two more filter errors return a 400 | The GetUser method answers a user that does not exist with a 404 "User not found." instead of a server error.
- A caller's filter that compares an xml field with
LIKE, or converts text that is not a GUID, now returns a 400 like the other caller filter errors.
- None of these cases adds an entry to
Development > Errors any more.
|
| Design > Data Sources - PDF downloads fetch only the site's own host names | PDF downloads from a data source now fetch pages only from host names your site lists, never from a host named in the request.
- A host name counts as your site's when it matches a Domain rule in
Admin > Friendly URLs, or equals the Web Site Primary Domain property in Admin > Properties.
- A Domain rule that matches any host, such as
.*, does not count.
- IP addresses, other ports, other host names and
file:// links return Page Not Found.
- A PDF requested from an
https page is never fetched over http.
Action needed: a site with no Domain rule and a blank Web Site Primary Domain returns Page Not Found for every PDF download. Add a Domain rule in Admin > Friendly URLs for each host name visitors use, or set Web Site Primary Domain.
|
| Site-wide - script Preview links open from a Console sign-in, with no website sign-in | The script Preview links in the Console now open for any Console user, including one signed in with Uber credentials, with no separate website sign-in.
- This replaces the 8.12.16 requirement to also sign in on the website before Preview, or
Forms > Forms Wizard View Preview and View Reports, would open.
- It covers the Preview links in
Design > Data Sources and the other module lists that open the script preview page.
- The page still shows no content to a visitor without Console access.
- Signing out of the Console or closing the browser ends preview access.
- Previewing an audience that only signed-in roles can see still needs a website sign-in.
|
| Master > Admin > Settings - passwords and keys are masked, and a Save is refused when the configuration changed | Master > Admin > Settings no longer sends stored passwords and keys to the browser.
Encryption Key, Email Password, Admin Impersonation Password, Sql SysAdmin Password and JWT Signing Key Secret are masked. A masked field shows that a value is set. Typing a new value replaces it, and leaving it blank keeps the current one.
- Each connection string is shown without its password. The password has its own masked row directly beneath it. A connection string that is not edited is saved exactly as it was.
JWT Signing Key Secret always has a row, even when no value is stored. The value must be Base64, and the Master and every site on the server must hold the same one.
- A Save is refused when the configuration files changed after the page was opened. The page reports that nothing was saved. Reloading the page and making the changes again completes the Save.
|
| Admin > Settings - passwords and keys are masked, and a Save is refused when the configuration changed | Admin > Settings no longer sends stored passwords and keys to the browser.
Encryption Key, Email Password and JWT Signing Key Secret are masked, as are Admin Impersonation Password and Sql SysAdmin Password on a site that has them. A masked field shows that a value is set. Typing a new value replaces it, and leaving it blank keeps the current one.
- Each connection string is shown without its password. The password has its own masked row directly beneath it. A connection string that is not edited is saved exactly as it was.
JWT Signing Key Secret always has a row, even when no value is stored. The value must be Base64, and the Master and every site on the server must hold the same one.
- A Save is refused when the configuration files changed after the page was opened. The page reports that nothing was saved. Reloading the page and making the changes again completes the Save.
|
| Development > Import Utilities - Custom Attributes saves only an .xml file name, in /Uploads/CustomAttributes/ | The Custom Attributes section of Development > Import Utilities now asks for an .xml file name and always saves the file in /Uploads/CustomAttributes/.
- A folder typed into File Name is ignored, so the file cannot be saved anywhere else.
- A name that is not an
.xml file is refused.
- The success message shows where the file was saved.
|
| Development > Utilities - Database Backup/Restore takes a file name, and the Master picks the folder | Development > Utilities > Database Backup/Restore now takes only a .bak file name. The Master chooses the folder.
- The default name is
cpweb_<SystemName>.Console.bak.
- When the Master's
SQL Backups Folder is set, the file goes there. The name must start with cpweb_<SystemName>., so a site cannot reach another site's backups or the Master's own site backup.
- When
SQL Backups Folder is empty, the file goes in the site's Backups folder, through SQL Server to Centralpoint UNC Path when that is set.
- A full path is refused. Until a site is updated, its old default path is refused.
- The Master's
App_Data\cpbak_Database.bak can no longer be restored here. Restore it from the Master's site backups.
If your database server is not on the web server, set SQL Backups Folder or SQL Server to Centralpoint UNC Path in Master > Admin > Properties before using this tool.
|
| Centralpoint Agent - the site's app pool can save settings kept in Local.config | Centralpoint Agent 8.12.17.5 gives each site's app pool write access to Root\Local.config when the file exists, as it already does for web.config. Without it, saving a setting kept in Local.config from Admin > Settings fails with an access-denied error, and Local.config is left unchanged.
|
| Site-wide - generating a missing Encryption.Key no longer copies Local.config settings into web.config | When a site has no Encryption.Key, Centralpoint generates one and saves it. That save no longer copies the settings from the site's Local.config into its web.config.
- If
Local.config declares Encryption.Key with a blank value, the new key is saved to Local.config.
- A local development copy of a site never generates a key. Set the server's current key in its
Local.config instead.
|
| Master > Admin > Settings - settings kept in Local.config are labeled and saved to Local.config, not web.config | On a Master with a Local.config, Master > Admin > Settings now keeps those settings in Local.config and never copies them into the Master's web.config.
- Each setting that comes from
Local.config is labeled "(Local.config, not encrypted)". Protected encrypts web.config only.
- Editing one of those settings changes it in
Local.config only, and the rest of that file stays as written.
- A
Local.config value changed by someone else after the page opened is not overwritten.
- If a save fails,
Local.config is put back as it was.
|
| Development > Utilities > Application Trace - no longer copies Local.config settings into web.config | Turning Application Trace on or off in Development > Utilities no longer copies the settings from a site's Local.config into its web.config. This matters on a load-balanced server, where Local.config holds that server's own values.
|
| Admin > Settings - settings kept in Local.config are labeled and saved to Local.config, not web.config | On a site with a Local.config, such as a load-balanced server, Admin > Settings now keeps those settings in Local.config and never copies them into web.config.
- Each setting that comes from
Local.config is labeled "(Local.config, not encrypted)". Protected encrypts web.config only.
- Editing one of those settings changes it in
Local.config only, and the rest of that file stays as written.
- A
Local.config value changed by someone else after the page opened is not overwritten.
- If a save fails,
Local.config is put back as it was.
|
| Master > CMS > Modules - saving a module's XML now refreshes the Development site | Saving a module with Edit Attribute XML in Master > CMS > Modules now restarts the Development site, so the Console shows the new attributes right away, as a normal module save already did.
- A save that matches no module now says so instead of reporting success.
- An error message from the save no longer breaks the confirmation alert.
|
| Admin > Configuration Changes - the Console now records who changed its settings, with a report | The Console now records each configuration change, with who made it and the before and after values, in the new Admin > Configuration Changes report.
- Recorded: module defaults, configuration and properties;
Site Architecture > Module Designer saves and version restores; Admin > Template Gallery installs; Development > Console Navigation saves; Admin > Properties; and the Reset Module Configuration tool in Development > Utilities.
- The report lists changes newest first with a one-line summary, such as "Changed 1 value: Description". Search by date range, change, object or user.
- Open a change to see what changed, then the full before and after values side by side.
- Password fields are never shown. They appear as
[secret], or [secret changed] when the value changed.
- Changes made with a Master or Uber login show the person's name, marked "(ancestor admin)".
- Only administrators can open the report.
|
| Admin > SAML MetaData - uploading the shipped Oxcyon.pfx is refused | The certificate upload in Admin > SAML MetaData refuses the Oxcyon.pfx certificate shipped with Centralpoint, under any file name, before anything is saved. Upload the site's own certificate instead. Other certificates upload as before.
|
| Admin > Global Login - the shipped Oxcyon.pfx is refused as a new SAML service provider certificate | Saving Admin > Global Login module properties is refused when SamlLocalCertificateFile is changed to the Oxcyon.pfx certificate shipped with Centralpoint, or a copy of it under another name.
- Re-saving a value that is already stored still works.
- Turning
SamlServiceProvider on while the certificate is that file is refused, since it puts the certificate into use.
- Changing only the password of that certificate counts as a change and is refused.
- A path that points at a folder or a file that cannot be read now shows the usual message instead of an error page.
|
| Admin > Deep Links - the shipped Oxcyon.pfx is refused as a new SAML IdP certificate | Saving Admin > Deep Links module properties is refused when SAMLIdPLocalCertFile is changed to the Oxcyon.pfx certificate shipped with Centralpoint, or a copy of it under another name.
- Re-saving a value that is already stored still works, so a site that has not moved to its own certificate keeps working.
- Changing only the password of that certificate counts as a change and is refused.
- A path that points at a folder or a file that cannot be read now shows the usual "not found" or "could not be opened" message instead of an error page.
|
| Master > Deployment > Web Sites - a new site no longer signs SAML with the shipped Oxcyon.pfx | Creating a web site from a parent no longer leaves the new site signing SAML as an identity provider with the Oxcyon.pfx certificate shipped with Centralpoint.
- When the parent's Deep Links certificate is that file, the new site's
SAMLIdPLocalCertFile and SAMLIdPCertPassword are cleared, and its identity provider entry is removed from saml.config.
- Set up the new site's own certificate in
Admin > Deep Links module properties, then send its new metadata to your SAML partners.
- Other uses of the file, such as the Global Login certificate or a partner record, are listed in the creation log and left unchanged.
- Restoring a site from a backup file changes nothing. Its uses are only listed.
- If the check fails, the site is still created, and the log says what to clear.
|
| Site-wide - a Master or website keeps serving for 72 hours when Uber cannot be reached | A Master or website that cannot reach Uber keeps serving for up to 72 hours from its last successful check, and Oxcyon is alerted.
- An unreachable Uber or UberControl no longer stops every site at once.
- A site that Uber answers as inactive, or refuses, still stops at once, and its 72 hours end.
- During the 72 hours the site asks Uber again every 5 minutes.
- Oxcyon receives one email when a site starts serving on the 72 hours and one when they run out.
- After the 72 hours the site stops until Uber answers.
|
| Design > Data Sources - the JSON link refuses a disabled data source | The JSON link of a data source now checks that the data source is enabled, the same check every DataSource CpScript and the Excel export make. A disabled data source returns a DataSource does not exist error instead of its rows.
- Anything that reads the JSON link of a disabled (On Hold) data source stops working after the update, such as a feed, an integration or an external system. Enabling the data source in
Design > Data Sources restores it.
- The JSON link of an enabled data source is unchanged.
|
| Centralpoint CLI - install shows why Uber refused to activate the Master | Centralpoint CLI 8.12.17.6 shows Uber's reason when it refuses to activate a new install, and stops asking to retry a refusal that cannot succeed.
- Reinstalling over a host name that already belongs to a Master needs that Master's enrollment code from Oxcyon. Run
centralpoint install --enrollment-code with it.
- Other activation errors still offer a retry, as before.
|
| Site-wide - signing keys Oxcyon has not approved are refused once the shared secret is off | Once Oxcyon turns off the shared signing secret for your server, your Master and its websites accept only signing keys Oxcyon has approved.
- Keys already approved keep working, and a key approved later works again within a few minutes.
- A new or rotated website key keeps working while its first report to Oxcyon is still pending.
- Servers whose shared secret is still on see no change.
|
| Site-wide - the Master's check-in no longer sends SQL passwords or secret settings to the Uber | When a Master checks in with Oxcyon's Uber, it now sends each website's connection strings without the User ID and Password, and blanks the secret settings.
- Properties that use the Password Box control are sent blank.
- API keys inside the
AIConfiguration property (OpenAI, Anthropic, Gemini and Azure OpenAI) are sent as ***REDACTED***.
- The Master's own settings go through the same redaction.
- Nothing changes on your server. The Uber never used these values.
|
| Development > Web API - the Error Log methods ask the Uber with a date and an id, not SQL | The Error Log methods of Development > Web API now send the Uber a start date or an error id, and no longer send SQL.
- The list and detail calls return the same errors as before.
- A request with an empty error id is refused.
|
| Development > Errors - the error list sends keywords, not SQL, to the Uber | Development > Errors now asks the Uber for its results with the search words, field, match type and sort order, and no longer sends SQL.
- Search, sorting, grouping and paging return the same rows as before.
- An
Errors.aspx?id= link opens that error, as before.
- A copy of the shipped encryption key can no longer be used to run SQL on the Uber through this list.
|
| Master > Development > Errors - the error list sends keywords, not SQL, to the Uber | Master > Development > Errors now asks the Uber for its results with the search words, field, match type and sort order, and no longer sends SQL.
- Search, sorting, grouping and paging return the same rows as before.
- An
Errors.aspx?id= link opens that error, as before.
- A copy of the shipped encryption key can no longer be used to run SQL on the Uber through this list.
|
| Admin > Global Login - a correct trusted certificate thumbprint no longer refuses every SAML sign-in | A Global Login record with a correct SAML Trusted Certificate Thumbprints value now signs users in. In 8.12.16 it refused every sign-in from identity providers that sign the assertion, such as Okta and Microsoft Entra.
- If you cleared a thumbprint because sign-in stopped working, you can set it again after this update. Sign in once right away to confirm it works.
- A response altered after signing, or signed with a different certificate, is still refused.
- A refused sign-in is now reported to Oxcyon with its reason, or with the thumbprint of the certificate that was offered.
- Failed SAML sign-ins are reported up to once an hour for each record and each cause, so one busy record no longer hides another record's failures.
|
| Site-wide - Console saves that rewrite a web.config are recorded for Oxcyon's Server Hub | A Console save that rewrites a site's web.config now sends Oxcyon's Server Hub a record naming the user, so the change is not reported as unexplained.
Admin > Settings (Root and Console web.config)
Admin > Properties (Console single sign-on)
Tools > Application Trace
Site Architecture > Search Page Designer
The record holds no values from the file. A save never waits on it, and an unreachable Server Hub does not affect the save.
|
| Master > Development > Sync Methods - two web.config checks now cover every site on the server | The checks for a public Trace.axd and for an unsupported target framework now read every site on the server, including sites in the default folder layout. Neither check runs on a local development copy.
|
| Master > Content > Scheduled Tasks > Sync - sites a patch skipped now also receive its web.config changes | When a patch skips a site that is still on an older version, the site's next sync now applies the patch's web.config changes, such as assembly redirects.
- The sync already copied the patched files and ran the patch's SQL. Now the site gets the matching web.config changes in the same pass, so new DLLs never run without their redirects.
- Each site receives a patch's web.config changes once.
- Only the site's Root and Console web.config change. A virtual directory that runs as its own IIS application keeps its own web.config, so apply the same change there by hand.
The same step runs from Master > Content > Scheduled Tasks > UpdateInstall for the Development site.
|
| Centralpoint Agent - reports ordinary activity precisely enough that it no longer raises Server Hub alerts | Centralpoint Agent 8.12.17.4 reports security and health evidence to Oxcyon's Server Hub more precisely, so ordinary activity raises fewer alerts.
- A single sign-on sign-in no longer counts as an account lockout.
- A Module Designer save is reported with the user who saved it.
- A changed web.config reports which sections changed, never their values.
- A site Api that fails to start (HTTP 500.30) reports its startup error, with passwords masked.
- Health checks probe only Centralpoint sites, and still probe a site whose web.config cannot be read.
- A failed sign-in count is not counted twice when a check-in is retried.
|
| Site-wide - the file upload dialog lets only administrators upload HTML files | The file upload dialog that opens from a module's file and document fields now lets only administrators upload .html and .htm files.
- For other users, HTML files are left out of the accepted types, and an HTML upload is refused.
- This covers both the standard upload window and the file explorer view of the dialog.
- Administrators and members of the Admins role can upload them as before.
- HTML files already in Uploads are not changed.
|
| Design > File Manager - only administrators can upload HTML files | Design > File Manager now lets only administrators upload .html and .htm files.
- Other Console users see "HTML files can only be uploaded by an administrator." and the file is not saved.
- Administrators and members of the Admins role can upload them as before.
- HTML files already in Uploads are not changed, and everyone can still see and open them.
- Other file types upload as before.
|
| Site-wide - SVG, XML and XHTML files opened from Uploads can no longer run script (web.config change) | SVG, XML and XHTML files opened directly from /Uploads or /PrivateLabeling no longer run any script in them.
- Covered types:
.svg, .svgz, .xml, .xsd, .xsl, .xslt, .xhtml and .xht. The files still display.
- An SVG shown in an image on a page is not affected.
- HTML, JavaScript, PDF, images and media are not affected, so e-learning courses under Uploads keep working.
- An XML file that uses an XSL stylesheet from Uploads now shows as plain XML.
- The change needs the IIS URL Rewrite module. A server without it gets no change, and the update reports it to Oxcyon.
web.config change
The update adds two <location> blocks to each site's and the Master's Root web.config, one for Uploads and one for PrivateLabeling. Each holds a URL Rewrite outbound rule named UploadsActiveContentCsp and is locked against child web.config files. The Console web.config is not changed.
- A
web.config under Uploads, or a virtual directory under Uploads running as its own IIS application, that defines its own URL Rewrite outbound rules returns a configuration error. Move those rules into the Root web.config.
- Custom pages that open an XML file with an XSL stylesheet from Uploads need to serve it from another folder.
|
| FormUpload CpScript - the Resource window's Replace keeps the stored file until the new one is in place | The Replace option in a FormUpload field's Resource window now keeps the resource's stored file until the new file is saved.
- Replacing with a file that already carries the resource's name, such as a downloaded copy, no longer deletes it.
- Replacing a resource whose stored file is missing from disk now restores it under the resource's name.
- A replace that cannot save the file shows "The file could not be saved. Please try again." The resource and its file stay unchanged.
- Replacing a
.pdf with a .xlsx removes the .pdf once the .xlsx is in place, and the resource's link serves the .xlsx right away instead of returning a 404.
- A file in the Resources folder with the same name as the upload is no longer overwritten.
This completes the resource upload fix in this version, which covered the upload button but not Replace.
|
| Development > Web API - request logs no longer store the access token from a GET call's URL | The site's request log no longer stores the access token a Web API GET call carries in its URL.
- A GET call sends its request, token included, as
?r={...} in the URL. The logged URL now shows the token as ***REDACTED*** and keeps the rest of the request.
- Other credentials in a logged URL or referrer, such as
access_token= or a JSON "Password", are hidden the same way.
- POST calls are unchanged. Their logged request body already hides the token.
- IIS logs on the server still record the full URL, so callers that can should send requests by POST.
|
| Site-wide - Word downloads always embed a working Word add-in token | A Word document downloaded for editing in the Word add-in now always carries a working add-in token.
- A user who had used the add-in before could get a blank token in every downloaded document, so saving from Word failed. Their next download now gets a working token.
- A token disabled in
Admin > Users > Access Tokens is no longer embedded; the next download gets a new one.
- Applies to
Data Transform > File Output Word output and the Procedure Manuals > Policies Word downloads.
|
| Api > WordAddIn - new Word add-in access tokens are stored as a hash only | The Word add-in now stores only a hash of each access token it issues, so reading the database no longer yields a working add-in token.
- Signing in and saving from the add-in work as before.
Admin > Users > Access Tokens lists these tokens, but View shows "Access Token Not Found" because no copy of the token is kept.
- A user with 10 or more add-in tokens gets a new token again; the oldest add-in tokens are removed, and the Word download token is never removed.
|
| Development > Errors - SQL conversion errors no longer show the value that failed to convert | Development > Errors no longer stores the value that a SQL conversion error quotes. The value can hold data the query read, so it is replaced with ***REDACTED***.
- This covers "Conversion failed when converting the ... value '...'", "The conversion of the ... value '...' overflowed" and "Error converting string value '...'".
- The rest of the message, such as the target data type, stays readable.
- A harmless value, such as a mistyped number, is hidden as well. To find it, rerun the query in SQL Server Management Studio.
|
| Master > Development > Sync Methods - a new check lists sites that sign SAML with the certificate shipped with Centralpoint | After the update, the Master checks every site for SAML settings that use the Oxcyon.pfx certificate shipped with Centralpoint. Every install that uses it shares the same certificate.
- The result lists each site and where the setting lives:
saml.config, a module property such as SAMLIdPLocalCertFile, or a record.
- A copy of that certificate saved under another name or folder is listed too.
- Nothing is changed. Replacing the certificate needs your SAML partners to import a new one, so it is scheduled with you separately.
|
| Site-wide - private key files can no longer be downloaded from any folder (web.config change) | Files ending in .pfx, .p12, .pem or .key can no longer be downloaded from any folder of the site, not only Uploads and PrivateLabeling.
- SAML sign-in keeps working, because the server reads its certificate from disk, not by URL.
- A file of these types that you share by URL, such as a
.pem certificate chain or a Keynote .key file, now returns 404. Share it through Resources instead.
web.config change
The update edits each site's Root web.config, the Master's Root web.config, and a load-balanced secondary's. Under system.webServer > security > requestFiltering > fileExtensions it adds <remove fileExtension=".pfx" /> followed by <add fileExtension=".pfx" allowed="false" />, and the same pair for .p12, .pem and .key. A <location> block that lists one of these types gets the same pair.
- A virtual directory that runs as its own IIS application inherits this rule. If its own
web.config adds one of these types, IIS fails every page under it with HTTP 500.19. Add a matching <remove> before that <add>, or delete the entry. The Master's Uploads review lists any such web.config.
- Custom code that serves one of these file types by URL needs the same fix, or a download page that reads the file from disk.
|
| ExportModuleResults Script Generator - the Excel export runs only the columns set in the generator | The Excel export from the ExportModuleResults Script Generator now runs only the columns set in the generator. A request cannot add or change columns.
- The
{ExcelMap} placeholder in the generator's scripts now renders a server-issued token, not the list of columns. A script that passes {ExcelMap} to the excelMap option works unchanged.
- A script that reads
{ExcelMap} as a list of columns, or a page that starts the Excel export by hand without the generator, must be changed to use the generator.
- When an export is refused, the visitor now sees a message asking them to reload the page.
- Exported Excel and zip file names now include a random part.
|
| Site-wide - sites no longer receive Local.config, and each site's dialog key moves into its web.config | The update and the site sync no longer copy Local.config, and every site keeps its own Telerik dialog key in its web.config.
- The 8.12.16 update copied one
Local.config with a single dialog key into each Master and Development site, and the site sync copied it on to every other site. Those sites then shared that key.
Local.config is now excluded from the update and from the site sync. Neither deletes a Local.config already on a site.
- The key update now replaces a dialog key that is still in
Local.config, and a machine key or dialog key that two sites on the same master share. It writes the new dialog key to web.config and removes the old entry. It deletes Local.config when that entry was its only setting, and keeps the file when it holds other settings.
- A site that already has its own keys in
web.config keeps them.
- Users on a site that gets new keys sign in again once. Open forms, Word Autofill links and open Telerik dialogs fail once.
- A key the update cannot rewrite is left as it is. An example is a Telerik key in an
appSettings section that a provider other than Windows data protection encrypts. The Sync Methods page shows that site as partly done.
web.config change warning
What changes. In the Root web.config of each site that gets new keys, the update replaces validationKey and decryptionKey in <machineKey> and sets validation="HMACSHA256" and decryption="AES". It writes the Telerik.Web.UI.DialogParametersEncryptionKey value to the appSettings of the same file and removes that entry from Local.config. It touches the Root web.config and Local.config only. The Console is a nested application under Root and uses Root's machine key, so Console users sign in again too.
Check these after the update.
- A virtual directory that runs as its own IIS application and shares sign-in with the site through its own
machineKey keeps the old key. Copy the new Root machine key into its web.config by hand.
- A second server that you load-balance by hand is not changed. Copy the Root machine key and the Telerik key to it right after the update, and keep that server's own
Local.config. Otherwise the two servers reject each other's sign-in cookies.
- Two sites that share a machine key on purpose, for shared sign-in, now get separate keys. Set the same pair in both again by hand.
- Custom code that shares forms tickets or
MachineKey data with another application needs a new shared pair. Set the same pair by hand in both applications.
|
| Master > Development > Process Log - the process list caps its offset | The process list refuses offsets above 10,000 and pages its keys before it reads their steps, so a large offset can no longer make the list slow.
|
| Centralpoint Agent and CLI - IIS repair reports its exception, and deployed files copy with retry | Centralpoint Agent 8.12.17.3 reports the exception type and message of a failed IIS app pool repair to Uber, with credentials removed.
Centralpoint CLI 8.12.17.5 and the deployment engine copy deployed files with retry and long-path handling.
- Both builds include updated hosting, management and cryptography packages.
|
| Site-wide - the 2019 Uploads/Local test page is removed from each Master | The unused 2019 test page under Root/Uploads/Local is removed from each Master when its files still match the shipped originals.
- Test.aspx and Test.aspx.cs are kept or removed together.
- A file you changed is kept.
|
| Site-wide - Console document saves retry after a database deadlock | Saving a document in the Console retries when the database picks it as a deadlock victim.
- A timeout is not retried.
- A bad
Site.Type setting now names the key and its value.
|
| Development > Errors - errors group by cause and name the data they refer to | The errors list records the cause of these faults more precisely.
- An unsigned web service call summary counts every failure reason.
- Faults in Centralpoint's own upload handlers no longer group with Telerik upload probes.
- A missing process or SAML source is recorded with the caller's text in a note.
- A relation-population lock wait is reported as contention.
- The Master names why the Agent pipe fell back when an app pool start or stop is denied.
- An aborted request no longer logs an error.
|
| Site-wide - the user details popup requires a signed-in administrator | The user details popup (User.aspx) opens only for a signed-in administrator, and returns a 404 to everyone else.
- Only an Oxcyon staff sign-in reaches the Uber copy of the account.
- The popup shows the user's name and email as text.
|
| Data Transform > Data Transfer - the file system reader skips Office owner files | The file system reader skips Office owner files (names that start with ~$), so an open document no longer breaks the transfer.
|
| Education > Test - questions in reports handle a blank correct answer | The questions-in-reports data no longer fails when a question has a blank CorrectAnswer.
|
| Procedure Manuals > Policies - saving with Conversion=PDF no longer fails on empty editor content | Saving a policy with Conversion=PDF no longer fails when its rich text editor has no content.
|
| CpAudienceSelector CpControl - honors isRepeated like the other selectors | CpAudienceSelector now honors isRepeated in the preview, like the other selectors.
|
| Site-wide - CpContent.DefaultView and DefaultRelationView return a new view on each call | CpContent.DefaultView and DefaultRelationView with a sort or filter return a new view each call. They no longer change the cached table's shared view, so two requests no longer race on it.
Custom code that relied on those calls changing the shared DefaultView must keep and use the returned view. The calls with no sort or filter are unchanged.
|
| Site-wide - searches skip an empty taxonomy selection, and Excel export rejects a blank search | A search with an empty taxonomy selection no longer fails the required-count check.
- Excel export refuses a blank encrypted search value instead of failing later.
- The export's
orderBy error names the right parameter.
|
| Api > AI - Anthropic and local-model providers move to updated libraries | The Anthropic provider uses Anthropic 13.6.0, and local models use LLamaSharp 0.30.0.
- A model download is written to a
.partial file and renamed when complete, so a site API never loads a partial model.
- If another site API finishes the same download first, this copy is discarded.
|
| Api > Data - a malformed query or files body returns a 400, and an API key needs a name | The Data API answers a malformed query or files request body with a 400.
- Creating or updating an API key without a
Name returns a 400.
|
| Development > Web API - a caller's bad filter, order or fields returns a 400 | GetUsers, ReadDetails and ReadResults return a 400 with a fixed message when the caller's own filter, order, fields or columns do not bind.
- A fault in the method's own configuration still reports as a 500.
UpsertDataModule checks its module lookup before it writes.
|
| Site Architecture > Audiences - the parent audience lookup uses a parameter | Editing an audience looks up its parent by id with a database parameter. Behavior for valid ids is unchanged.
|
| Site Architecture > Site Wizard - the parent audience lookup uses a parameter | Creating an audience in the wizard looks up its parent by id with a database parameter. Behavior for valid ids is unchanged.
|
| Master > CMS > Navigation - the parent navigation lookup uses a parameter | Editing a navigation item looks up its parent by id with a database parameter. Behavior for valid ids is unchanged.
|
| Development > Import Utilities - Extract SharePoint Documents starts its progress entry first | Extract SharePoint Documents starts its process entry before it reads its settings, so a failure is reported in the process log.
- A call with an unset process key is skipped.
|
| Site Architecture > Module Designer - saving a module view retries when its file is locked | Saving a module view retries up to five times when an editor or a virus scan holds the generated .ascx file, instead of failing the save.
|
| Development > Code File Manager - the website selector's --Select-- entry does nothing | Choosing --Select-- in the website list no longer sets an empty root path.
|
| Site-wide - resource upload replaces the file safely, and an empty resource id returns a 404 | Replacing a resource's file keeps the old file until the new one is in place.
- Uploading a file that already carries the resource's name no longer deletes it.
- A failed replace shows a message and leaves the record unchanged.
- Replacing a
.jpg with a .png removes the .jpg.
- The stored original file name now shows the new upload's name.
Resource.ashx answers an empty resource id with a 404.
|
| Site-wide - the file upload dialog answers a refused request with a plain 404 and records it | The file upload dialog refuses a request that has no JavaScript, no dialog value, a dialog value it cannot read, or an invalid subfolder.
- The refusal is a plain 404 in the current application. It no longer redirects to a sign-in page on a site behind single sign-on.
- The first refusal each minute is recorded as
FileUpload:Refused, with the reason and request details.
|
| Design > File Manager - New Folder works when the folder was opened from the grid | New Folder no longer fails when you opened the current folder from the grid instead of the tree.
|
| Admin > Global Login - IdP-initiated SAML sign-in works after an SP-initiated attempt | SAML sign-in started from the identity provider now works after a sign-in started from the site.
- A missing or unsupported SAML source is named in the error, and the sign-in is still refused.
- A domain controller timeout is treated as a sign-in problem, not reported as an error.
|
| Admin > Roles - dynamic roles accept Contains and Does not contain filters on lookup fields | A dynamic role built with Contains or Does not contain on a lookup field now selects the right users.
- The
DynamicRoles job leaves the members of a role whose query fails unchanged.
- The process status names the failed roles and the SQL error number.
|
| Master > Content > Scheduled Tasks > CreateResourceFromZip - a locked source file is skipped instead of stopping the task | The CreateResourceFromZip task skips a file another program still holds open and imports it on the next run.
- A copy in progress or a virus scan no longer stops the whole run.
- A file that cannot be deleted is renamed aside.
- A read-only file is imported as before.
|
| Master > Content > Scheduled Tasks > Sync - the data sync repairs drifted outline tables and names a mismatched one | The data sync no longer fails when an outline table has lost its ModifyDate column.
- A sync method adds the missing
ModifyDate (and ModuleId for the cpsys_DataCurrent outline) on every site.
- The data sync copies outline rows by column name, so a mismatched outline is named in the error.
- The sync-method catalog refresh skips a Development site that no longer exists and clears its cached id.
|
| Site-wide - values named like a connection string are redacted like passwords | A value whose name ends in ConnectionString, such as SourceSqlConnectionString, is now redacted wherever values named like Password already are.
- Request headers stored with Api errors on
Development > Errors.
- Sample data the JSON data source writes to the page trace.
- The logged request body in the Web API request log.
|
| Development > Web API - methods skip Web API, Authentication Sources and Email Access records, and hide credentials | Web API methods no longer read or write records in the Web API, Authentication Sources or Email Access modules, and read results leave out credentials from every other module.
ReadDetails, ReadResults and DataTables never return those modules' records, even when the method has no module set.
UpsertData, DeleteData and site-to-site upsert refuse those modules. Site-to-site upsert now also skips Email Access records.
- Read results leave out properties and columns named like a credential, such as
Password, ConnectionString, ClientSecret or ApiKey, including inside the Attributes value.
- A request
Filter or OrderBy gets a 400 when it references Attributes, AttributesJson, Configuration, a credential-named column, a full-text predicate such as CONTAINS, or a non-ASCII name.
Writes are unchanged: an UpsertData method can still set a Data Sources ConnectionString.
|
| Site-wide - the rich text editor dialog shows an unknown view name as text | The rich text editor's Media Manager and Site Links dialog now shows an unrecognized view name as plain text. A crafted link to the dialog can no longer add markup to the page. Media Manager and Site Links work as before.
|
| Broadcasts > Broadcasts - the member filter builder treats its field name as text | The member filter builder in Broadcasts > Broadcasts now treats the field it fills as plain text. A crafted link to the builder can no longer run script in your Console session. Opening the builder and saving a filter work as before.
|
| Development > Errors - error details display as text, and detail links open only web addresses | Development > Errors now shows every error detail as plain text, so a value recorded from a visitor's request can no longer run in your browser when you open the error.
- The visitor's browser, host, user name, audiences, page path and request type show as text.
- The Generation Exception keeps its line breaks and shows the rest as text.
- The URL, Referrer and Help Link fields open only
http and https addresses. Any other address shows as text and does not open.
- The Help Link opens in a new tab without access back to the Console tab.
|
| Development > Web API - Eventbrite and site-to-site methods are restricted, and request logs hide credentials | Web API methods now refuse a few unsafe requests, and the Web API request log no longer stores credentials.
- An Eventbrite method only fetches events from
https://www.eventbriteapi.com/v3/events/. Any other api_url gets a 400, and the stored EventBrightOAuthToken is never sent anywhere else.
- A method that copies records from another site on the same server skips records in the Web API and Authentication Sources modules, with the warning "DataId ... was not upserted because its module is excluded from site-to-site upsert." Records from other modules still copy, including into a different module.
- With Web API logging turned on, the logged request body shows
***REDACTED*** in place of Token, NewPassword, passwords, keys, secrets and user credential fields.
|
| Site-wide - module searches accept only supported field names | Module searches now check every search field name before the search runs. This covers a form's SearchField, the TemplateAjax module's search state and the fields query string.
- Supported field names keep working: a column,
table.Column, cpsys_Search, cpsys_Taxonomy, and type-prefixed names such as DateTime:ModifyDate.
- An unsupported field name with a search value returns no results instead of running the search.
- Multi-part forms such as
In:..., Roles:... and Taxonomy:... are no longer accepted from search requests. Console grids are not affected.
- A field name containing a brace no longer causes a server error.
A custom search form that posts a multi-part field name now returns no results and needs a supported name.
|
| Data Transform > Search Results Output - the selected output's HTML is always loaded from the server | Site search pages now load the selected Search Results Output's DownloadHTML from the server on every render, instead of from values the browser sends back.
- Only an output listed in the search page's
SearchResultsOutputs property can be shown.
- If a visitor's selected output is removed from that list or unpublished, the page shows the standard results instead of an empty results area.
- The search page no longer writes each output's HTML into hidden form fields.
|
| Site-wide - search downloads, Excel exports and DataTables buttons run only the search the server built | Search result downloads, the Export Module Results script and the SystemPageAjaxDataTableSearchButton CpScript now run only the search the server built for the page. The browser receives a short token instead of the search itself.
- Covers the Search Results Output download options on the site search page, Export to Excel on module results and AJAX module results, and the site search DataTables buttons.
- Any search details the browser sends back are ignored.
- A token works only in the browser session that loaded the page, and only for the user signed in at the time.
- After signing out, 20 idle minutes or an application restart, the page must be reloaded before exporting again.
- Custom code that decrypted the search fields sent to the browser no longer receives them and must be updated to post the token back.
|
| Site-wide - the attribute list popup shows a nav item's attributes only to users who can open it | The attribute list popup, opened from a module's Custom Attributes help link or from Admin > Properties, now shows a nav item's attributes only to users who can open that nav item. The Users, Audiences, Taxonomy, Ecommerce and Resources property lists require Admin > Properties. The default attribute list still opens for every Console user.
|
| Surveys > Questions - the per-question survey popups require survey access | The per-question survey popups, opened from Surveys > Questions, now open only for users who can open Survey Results, Surveys or Questions.
|
| Development > Web API - the field mapper requires Web API access | The Web API Field Mapper now opens only for users who can open Development > Web API.
|
| Forms > Forms Wizard - the user fields list requires Forms Wizard access | The user fields list inside Forms > Forms Wizard now loads only for users who can open the Forms Wizard.
|
| Forms > Forms - the field map builder requires Forms access | The field map builder, opened from a form's Field Map, now opens only for users who can open Forms > Forms.
|
| Tools > Forms Reporting Wizard - the form select command builder requires a module that opens it | The form select command builder now opens only for users who hold the Tools > Forms Reporting Wizard nav item, or can open Data Sources or Report Builder.
|
| Tools > Data Source Wizard - the select command builder requires a module that opens it | The select command builder now opens only for users who hold the Tools > Data Source Wizard or Tools > Actionable Select Command Builder nav item, or can open Data Sources, Report Builder, Broadcasts or Export to inDesign.
|
| Tools > Complex Query Builder - the popup from Data Sources requires the builder or Data Sources access | The Complex Query Builder popup, opened from a data source's SQL Query link, now opens only for users who hold the Tools > Complex Query Builder nav item or can open Design > Data Sources.
|
| Tools > Actionable Select Command Builder - the popup from Forms Wizard requires the builder or Data Sources access | The Actionable Select Command Builder popup, opened from the Forms > Forms Wizard link, now opens only for users who hold the Tools > Actionable Select Command Builder nav item or can open Design > Data Sources. The builder creates a data source from the query you enter, so Forms Wizard access alone is no longer enough.
|
| Design > Data Sources - the JSON preview and the Facebook, Slack and Yammer token wizards require Data Sources access | The JSON feed preview and the Facebook, Slack and Yammer authorization token wizards now open only for users who can open Design > Data Sources. Administrators can open them from any audience.
|
| Site-wide - a record's audit trail opens only for users who can open the record's module | The Audit button on a module record now opens the audit trail only for users who can open that record's module. Administrators can open every audit trail. An invalid record id shows "Invalid Id" instead of an error page.
|
| Ecommerce > Orders - billing details are shown to administrators only | On Ecommerce > Orders, the "Click here to see billing info" link and the billing details it opens are now available to administrators only. Other users who can open Orders see "N/A" in the billing field.
|
| Broadcasts > Broadcasts - the member filter builder opens only for Broadcasts users and rejects unsafe filters | The member filter builder, opened from a broadcast's Custom Filter, now opens only for users who can open Broadcasts > Broadcasts.
- Preview rejects a saved filter that contains
;, --, /*, or unbalanced quotes or parentheses, and shows "Your SQL Filter is Invalid". Values typed into the condition boxes, such as Acme (West, are accepted.
- A condition with an invalid column name, or a number or true/false column with a value that is not a number or true/false, is rejected.
- Preview no longer shows database error text.
- Values with an apostrophe, such as
O'Brien, now work.
- Build keeps the broadcast's existing filter and adds the new condition, as before.
|
| Data Transform > Data Transfer - restoring a backup also requires Data Transfer in your current audience | Restoring a module backup from Data Transform > Data Transfer now also requires that a Data Transfer nav item is available in the audience you are working in. Administrators restore backups as before from any audience that includes Data Transfer.
|
| Development > Import Utilities - a nav item with no panel shows non-administrators only the panels they hold | A user who is not an administrator and holds only the plain Development > Import Utilities nav item now sees only the import panels whose own nav items they hold, and can run only those.
- Administrators still see and run every panel from the plain nav item.
- To give a user an import tool, grant that tool's own nav item, such as
Change Full Text Index.
- The
Resource Access Diagnostic nav item now opens its panel.
|
| Development > Utilities - a Utilities nav item with no panel shows non-administrators only the panels they hold | A user who is not an administrator and holds only the plain Development > Utilities nav item now sees only the utility panels whose own nav items they hold, and can run only those.
- Administrators still see and run every panel from the plain nav item.
- To give a user a utility, grant that utility's own nav item, such as
New Guid or Database Backup.
- A utility nav item whose display value ends in a space now opens its panel.
|
| Development > Web API - GetUsers and GetUser no longer return password hashes, credentials or Configuration secrets | The GetUsers and GetUser Web API methods no longer return password hashes, stored sign-in credentials or secret Configuration properties.
GetUsers returns a 400 when Filter, Fields or Columns names PasswordHash or AuthenticationSourcesCredentials. Neither column is returned.
- With
ReturnConfiguration, Configuration is returned without ImportedPassword, OwaPassword, AccountVerificationKey, PasswordChangeVerificationKey or the OAuth token properties. Stored values are unchanged.
- In
GetUsers, Configuration can be selected only under its own name, and a Filter that mentions Configuration returns a 400.
Integrations that filter on Configuration or read AuthenticationSourcesCredentials through GetUsers need updating.
|
| ExtAutoComplete CpScript - user lookups require sign-in and return only user names, display names or emails | The ExtAutoComplete CpScript's user lookup (a SystemName of cpsys_Users) now returns suggestions only to signed-in users.
- The
Relation Field Name must be UserName, DisplayName or Email. Any other field returns no suggestions.
- Visitors who are not signed in get no suggestions, and no setting turns this back on.
- Custom pages or integrations that call the AutoComplete web service directly for
cpsys_Users follow the same rules.
- Module lookups and the
ExtAutoCompleteRedirect CpScript are unchanged.
|
| Site-wide - Developer Login checks access first and counts failed passwords toward the Console sign-in lockout | The Developer Login page (/Console/DevLogin.aspx) now checks that you are allowed to switch users before it checks any password.
- Only an Oxcyon staff developer signed in to the Console can use the page. Anyone else sees "You don't have access to this feature." and no password is checked.
- Failed passwords on this page now count toward the Console sign-in lockout added in 8.12.16. Ten failures for one username, on the Console sign-in page and this page combined, lock that username for 15 minutes.
- The page no longer tells a user without access that the password they entered was correct.
|
| Site-wide - changing an upload field's folder no longer shows server error details | When switching an upload field's folder in a Console module form fails, the message now reads "Change upload directory failed." It no longer shows server file paths or code details.
|
| Data Transform > Data Transfer - only administrators can restore a module backup, and only into its own module | Restoring a Data Transfer module backup now requires an administrator, and the backup must belong to the record's destination module.
- The Restore Backup button shows only for administrators.
- A restore is refused when the backup holds no records for the destination module, so a restore can no longer empty a module.
- If a Data Transfer's destination module changed after its backup ran, that backup can no longer be restored. Set the destination back to the original module to restore it.
- A restore into a module without a relation now completes instead of reporting a failure.
- When a restore fails, the message no longer shows server file paths or code details.
|
| Master > Development > Errors - error fields and details display as text | Master > Development > Errors now shows every field of a reported error as plain text, so markup inside an error report cannot run in your session.
- The error list's Stack Trace and Web Site columns show their text exactly as reported.
- On an error's details, Error Key, Stack Trace, Web Site and Update Version show as text.
- Every field under Details shows as text, and the Stack Trace box keeps its line breaks.
- The Help Link, URL and Referrer links under Details open only web addresses (http or https). Any other value is shown but does not link.
|
| Master > Development > Utilities - the test page and the Bin comparison page require the Utilities roles | Two Development pages with no menu item of their own now open only for users with LimitedAdmins, Developers or Admins, the same roles as Utilities:
- the test page (
Test.aspx)
- the custom Bin comparison page (
Uploads/Utilities/Utility.aspx)
Other users are sent to the Master home page.
|
| Master > Deployment > Web Sites - the site tree requires the Web Sites roles | The site tree view of Deployment > Web Sites now opens only for users with LimitedAdmins, Deployers or Admins, the same roles as Deployment > Web Sites. Other users are sent to the Master home page.
|
| Master > Development > Health Monitor - the All Records view requires the Health Monitor roles | The All Records view of Development > Health Monitor now opens only for users with LimitedAdmins, Developers or Admins, the same roles as Health Monitor. Other users are sent to the Master home page.
|
| Master > Development > Map Relationships - the page opens only for its roles | Development > Map Relationships now opens only for users with LimitedAdmins, Developers or Admins, the roles on its menu item. Other users are sent to the Master home page.
|
| Master - every page method requires a role on its page | Every page method on the Master now requires one of the roles that open its page, as listed on the page's menu item.
- Users with the Admins role are unaffected.
- A call from a user without those roles is refused.
- A page method on a page with no menu item is refused for everyone.
Deployment > Web Sites create and delete, Deployment > Updates, Deployment > My Updates, Deployment > Synchronize, Development > Health Monitor clear and export, Development > Map Relationships and CMS > Keyword Lists also check the caller's roles inside each action.
Content > Web Sites: renaming a site's system name requires access to that site.
Custom code
A custom Master page with page methods and no menu item of its own now gets an error on every call. Tell Oxcyon about any such page before updating, so it can be given roles.
|
| Master > Deployment > Synchronize - a file edited on a child site is no longer replaced by the parent's older copy | Master > Deployment > Synchronize no longer replaces a file edited on a child site with the parent site's older copy. Since 8.12.16, every sync reverted those edits.
- This covers the site's files, and with Sync Data, its
Uploads, Resources and App_Data files.
- The parent's copy still replaces the child's when the parent's file changed since the last sync, or when All Elements is ticked.
- A file that exists only on the child site is still removed, as before.
- Files an 8.12.16 sync already reverted do not come back on their own. Restore them from a backup or make the edit again.
- A load-balanced secondary server is still kept an exact copy of its primary.
|
| Centralpoint CLI - site and server migrations carry SAML certificates | Centralpoint CLI 8.12.17.1 copies a site's SAML certificates into the destination install's Certificates folder when it migrates a site or a whole server.
- Only the certificates the site's
saml.config and its Global Login or Deep Link records name are copied.
- If a different certificate with the same name is already in the destination, it is kept and the migration reports an error.
- When the CLI sets file permissions, the site's app pool gets Modify on the install's
Certificates folder.
|
| Centralpoint Agent - copies SAML certificates to load-balanced secondary servers | Centralpoint Agent 8.12.17.1 keeps the install's Certificates folder in step on a load-balanced secondary server, so SAML sign-in works on both servers.
- When it starts, the Agent copies every certificate to the secondary and gives the site's app pool access to the folder.
- A new or changed certificate on either server is copied to the other, and the newer file wins.
- A delete is never copied, so removing a certificate on one server never removes it from the other.
- A site sync also copies the certificates to the secondary.
Load-balanced clients: after installing, check that the secondary's Certificates folder holds the same files as the primary.
|
| Master > Deployment > Synchronize - Data Sync no longer deletes SAML certificates in Uploads | Master > Deployment > Synchronize with data no longer deletes a site's .pfx, .p12, .cer or .crt files from Uploads when the parent site does not have them.
- Other files the parent does not have are still removed, as before.
- A folder the parent site does not have at all is still removed whole, with any certificates in it. This is tracked separately (#2118). Certificates moved to the
Certificates folder are not affected.
- A Data Sync to a site on another install copies the certificates the site's records use into that install's
Certificates folder. Sites on the same install share one folder, so nothing is copied.
|
| Master > Content > Web Sites - backups carry the site's SAML certificates and restore them | A site backup now includes the SAML certificates its Global Login and Deep Link records use, and restoring or creating a site from that backup puts them back in the Certificates folder.
- A certificate already in place with the same contents is left alone.
- If a different certificate already has that name, the live one is kept and the restore reports an error. The backup's copy is left in
Root\App_Data\cpbak_Certificates for you to compare.
- Restoring a backup taken before 8.12.17 puts its certificates back in
Uploads (see the Site-wide note).
|
| Admin > SAML MetaData - uploaded certificates go to the Certificates folder | A certificate uploaded on Admin > SAML MetaData is now saved in the install's Certificates folder instead of Uploads, so it can no longer be downloaded by URL.
- The certificate value becomes
../../../Certificates/<file>.
- Uploading the same certificate again reuses the saved file.
- A file that is not a certificate, a file that does not open as a certificate, or a reserved Windows name such as
CON.pfx is refused.
|
| Admin > Deep Links - turning on SAML encryption with a certificate that does not load is refused | Admin > Deep Links now refuses to turn on SAML encryption when the encryption certificate does not load, so a bad certificate can no longer break SAML sign-in for the whole site.
- The save shows an error and nothing changes, including
saml.config.
- A new or changed certificate value that is missing or does not open is refused the same way.
|
| Admin > Global Login - certificate values that do not load are refused on save | Admin > Global Login now refuses to save a SAML certificate value that does not load, so a typo can no longer break SAML sign-in for the whole site.
- Saving a record or the module properties with a new or changed certificate file that is missing or does not open shows an error, and nothing is saved.
- Turning on SAML Service Provider with a certificate that does not load is refused.
- Values that did not change are not re-checked, so existing records keep saving.
Check before installing: a SAML Partner Certificate File that starts with / or \ is now loaded, where before it was ignored. An enabled record with SAML Use Embedded Certificate = Yes and no thumbprint is then pinned to that file, and a sign-in signed by any other certificate is refused. Confirm the file matches the identity provider's current signing certificate, or add the thumbprint.
|
| Site-wide - SAML certificates move out of Uploads into the install's Certificates folder | SAML certificate files (.pfx, .cer) now live in the install's Certificates folder, beside WebSites, instead of under a site's Uploads folder.
- The update moves each certificate that a Global Login or Deep Link record names from
Uploads to Certificates. It updates the records, their history and saml.config to the new location, then deletes the Uploads copy.
- A certificate that cannot be moved stays where it is and keeps working. The update lists it in its report.
- A certificate outside
Uploads, such as one in App_Data, is left in place.
- Restoring a backup taken before 8.12.17 puts its certificates back in
Uploads. The move does not run again on its own. Contact Oxcyon support to run it again after such a restore.
|
| Education > Assignments - the Assignment Details view requires sign-in and accepts only a valid assignment id | The Education Assignment Details view (?assignmentdetails=1&did=...) now shows assignment details only to signed-in users and only for a valid assignment id.
- A signed-out visitor sees only the "not accessible" message. The assignment's title, description and program list no longer appear beneath it.
- An id that is not a valid assignment shows an empty view instead of running a lookup.
- Program lists and target completion dates for signed-in users are unchanged.
- A site whose Assignment Details view was saved in the Module Designer runs its own copy of the view. Resubmit that view in the Module Designer to apply this change.
|
| Admin > Properties - Console Utilities Require Signature removed, unsigned Console service calls always refused | The Console Utilities service now refuses every unsigned or wrongly signed call with a 403, on every site.
- The
Console Utilities Require Signature property is removed from Admin > Properties. There is no setting to serve unsigned calls again.
- The Master and your site's front end already sign every call, so forms, Data Transfer, Retention and Master property pushes keep working.
- A refused call is recorded in
Development > Errors as ConsoleWebServicesAuth:Rejected, with the caller's address and the likely cause, at most once a minute.
Check before you install
- Custom code that builds its own
Console.Utilities proxy gets a 403. Change it to SignedConsoleUtilities.
- An
*Async or Begin* call on SignedConsoleUtilities is not signed and gets a 403. Change it to the synchronous method.
- An outside system that posts to the Console
Utilities service directly can no longer use it.
- The Master and the site must use the same
JWT.Signing.Key.Secret value. If they differ, Data Transfer, Retention and property pushes from the Master are refused.
- Look in
Development > Errors for ConsoleWebServicesAuth:Unsigned rows from the last few weeks. Each one is a caller that this release refuses.
|
| Master > Development > Map Relationships - removed an unused sample Access file from Uploads | The Master no longer keeps the sample file 2Kubotas.accdb in Uploads/MapDynamicRelationships.
- The update deletes the file from each existing Master. A Master that does not have it is left as it is.
- The
MapDynamicRelationships folder stays, and Master > Development > Map Relationships uploads work as before.
- New Masters no longer receive the file.
The file held sample data and nothing used it. Until this release, a site served Access files from Uploads to anyone who knew the URL.
|
| Centralpoint Agent - runs sync methods itself when the server's CLI is older than 8.12.15 | The Centralpoint Agent now hands sync methods to the Centralpoint CLI only when the CLI is 8.12.15 or later. With an older CLI, the Agent runs the sync method itself through a signed call to the Master, so sync methods keep working on Masters that refuse unsigned calls.
A sync method that affects the Agent's own connection can report its result a little late in this case. A retry skips the work that already finished.
|
| Master > Utilities, Sync and Scheduled Tasks web services - calls without a valid signature are always refused | The Master's Utilities, SyncInvokeMethods and ScheduledTasks web services now refuse every unsigned or wrongly signed call with a 403.
- Until now the Master still served unsigned calls while any site, the Agent or the CLI was below 8.12.15. That window is closed.
- Every site, Agent and CLI at 8.12.15 or later already signs its calls, so nothing changes for them.
Check before you install
- Sites below 8.12.15 on the same Master lose every call to the Master, including Console Clear Cache and sync methods. Sync them first, and delete any site row in
Master > Content > Web Sites for a site that no longer exists.
- An Agent or CLI below 8.12.15 can no longer run scheduled tasks or sync methods. Update it first.
- Custom code that calls
Master.Utilities through its own proxy, instead of SignedMasterUtilities, gets a 403. Convert it before installing.
|
| Master > Admin > Settings - the signing key shows at the top of the page, and a save names its user to Oxcyon | Master > Admin > Settings now shows the signing key in a new System Signing Key section at the top of the page. It is no longer under Page Options > Show/Hide Properties.
- Node shows this server's name.
- Signing Key Fingerprint shows the fingerprint on its own.
- When Oxcyon asks you to confirm the key, you can send the fingerprint or the whole Node and fingerprint line.
- Saving the page now reports the save and your user name to Oxcyon, so the
web.config change it makes is recorded as a settings save and not reported as a possible intrusion. The save does not wait for this report, and a failed report never stops a save.
|
| Design > Script Generator - Export Module Results zips only files from records the visitor can see | The Export Module Results download now zips attachments only from records the visitor is allowed to see, by their roles and tenant. A signed-out visitor no longer gets files from records limited to signed-in users or to other roles. Administrators still get the files of every record they select.
|
| Data Transform > File Output - policy and manual output requires access to the record | File Output links that name a policy or manual (policyId or manualId) now check that the visitor is allowed to see that record, by its roles and tenant. A record the visitor cannot see, or one that does not exist, returns Page Not Found. Scheduled and archived policies still output for visitors who can see them, and records from child audiences still work.
|
| Admin > SAML MetaData - the metadata download serves only the IdP and SP files | The SAML metadata download link (SamlMetadata.ashx) now serves only the IdP and SP metadata files that Admin > SAML MetaData generates. Any other request returns Page Not Found.
|
| Site-wide - downloads, zips, PDF conversion and file viewers refuse backup, log, config and system files | Files a visitor cannot open by URL can no longer be pulled out through a download, zip, PDF conversion or file viewer either.
- Zip downloads (the
DataSource module zip, Module Results and File Output zips) and the Web API data/files download leave out backup, log, database and source files (.bak, .log, .sql, .mdb, .accdb, .cs), configuration files (.config) and the site's own page code (.aspx, .ashx, .master and similar).
- They also leave out anything in the site's
App_Data, App_Code and bin folders.
- PDF creation from a link (
Pdf.aspx), AsposeToPdf, AsposeToImg, and the Word and Excel viewers, including the Excel viewer's download button and saved previews, now refuse private key files and the Data Transfer and custom attribute folders, the same as zip downloads.
- Ordinary files under Uploads download, zip and display as before.
|
| Admin > Users - the set-password link works on sites with Console single sign-on | When you create a Console user or reset a password, the emailed set-password link now opens the Console's Set Password page on every site.
- On a site with the
ClientConsoleSso property turned on, the link opened a missing page on the website. It now opens /Console/SetPassword.aspx.
- Sites without Console single sign-on send the same link as before.
Master > Admin > Users is not affected.
|
| Centralpoint Agent - keeps the Master Api running after a recycle, and lets a re-sent patch finish | Centralpoint Agent 8.12.16.23 restarts the Master Api after an update or patch recycles it, so the Master registers its signing keys.
- The site health check now starts a sleeping Master Api instead of skipping it. Website app pools still sleep as before.
- The API outside-callers security check now reaches the Master Api through the Master site's own IIS binding when the public address does not answer. This covers TLS offloaded upstream, an IP-bound site, and a different IIS port.
- A pool-recycling patch sent again after it ran out of time now skips files it already copied, and stops only the app pools with files left. On a server with many app pools, the patch can now finish.
|
| Site-wide - Console Clear Cache and Restart Application work again | The Console's Clear Cache and Restart Application options work again. In 8.12.16 both did nothing when clicked.
- Clear Cache is available to every Console user, as before.
- Restart Application now requires the LimitedAdmins or Admins role on the server, matching who sees the option. Other Console users can no longer restart the site by calling it directly.
- Signed-out requests to either option are still refused.
|
| Design > Script Generator - AutoComplete searches run only the SQL the configuration wrote | AutoComplete searches now run only the filters, joins, sort orders and columns written in the page's Script Generator AutoComplete configuration.
- A search request that sends any other SQL, or comes from outside the page, gets "The search could not be completed."
HasSystemFilter: false and searching every module apply only when the configuration sets them.
- A search returns at most 100 results, and error messages no longer show details.
- A value built in JavaScript instead of written in quotes, such as
CustomFilter: getFilter(), or one that holds a CpScript tag, now stops that configuration's searches. Rewrite it as a quoted value in AutoCompleteStartupScripts.
- Custom code that calls the AutoComplete web methods directly is refused. Call them from a page that renders the configuration.
- Clear the page cache after the update. A page cached before it cannot search.
|
| Api > SystemSigning - the Master rotates website signing keys and retires the keys of removed websites | Each website's system signing key is now rotated by its Master, so a website keeps a current key even when its own Api is idle.
- When a website is deleted, or its Root folder is removed, the Master retires that website's signing keys and tells Uber.
- A website key that has gone 14 days past its rotation date is retired, even when its website still exists.
- A website restored after its key was retired receives a new key automatically.
- Setting
SystemSigningKeyRotationDays to 0 turns off both rotation and the overdue retirement.
The Master Api must be able to write each website's Root\App_Data\SystemSigning folder. If it cannot, that website's key is not rotated and is retired once it is overdue.
|
| Site-wide - private key files under Uploads can no longer be downloaded (web.config change) | Private key and certificate bundle files under Uploads and PrivateLabeling can no longer be downloaded by URL. This protects SAML signing keys, such as the default Uploads/SAML/idp.pfx.
- Blocked types:
.pfx, .p12, .pem and .key. The files stay where they are and SAML sign-in keeps working.
- A page or link that serves one of these files directly from
Uploads will now get an error.
web.config change
The update adds these entries to the Uploads and PrivateLabeling location blocks in each site's Root/Web.config, including the Master and a load-balanced secondary: <remove> then <add allowed="false"> for .pfx, .p12, .pem and .key.
- A virtual directory that runs as its own IIS application has its own
web.config, which the update does not touch. Add the same entries there by hand if it holds key files.
- Custom code that serves one of these file types from
Uploads by URL must move the file or serve it another way.
|
| Api > Data - file downloads leave out private key files and Data Transfer and custom attribute files | Data API file downloads no longer return private key files, or files in Uploads/DataTransfer or Uploads/CustomAttributes.
- Key files are
.pfx, .p12, .pem and .key.
- The rule also applies when Uploads is moved with the API's
VirtualDirectories setting.
- A file path that names an NTFS stream is refused.
A refused file is treated the same as a missing one. When no files remain, the download returns No Files Found.
|
| Site-wide - zip downloads leave out private key files and Data Transfer and custom attribute files | Zip downloads no longer include private key files, or files in Uploads/DataTransfer or Uploads/CustomAttributes.
- This covers Data Source zip downloads, module results file downloads, and custom code that builds a zip with
CompressionService.CreateFromArray.
- Key files are
.pfx, .p12, .pem and .key.
- The rule also applies when Uploads is moved by an IIS virtual directory.
Other files in the same request are still included. If every requested file is refused, some pages return an empty zip instead of a "no files" message.
|
| Data Transform > File Output - download selected returns only the visitor's own generated files | Downloading selected File Output documents now returns only files generated for the person downloading them.
- A request for any other file, including another user's generated documents or system files, returns an empty zip and leaves the file in place.
- Private key files are never included.
- Only the files that were returned are removed afterward.
Visitors who are not signed in share one folder, which holds only their own generated documents.
|
| Master > Admin > Properties - new Webhook Allowed Internal Hosts property | The new Webhook Allowed Internal Hosts property lists the internal hosts a webhook may post to. It is empty by default, so every internal address is refused.
- Enter host names, addresses or ranges separated by commas, for example
intranet.example.local, 10.0.5.20, 10.0.5.0/24.
- A host name is trusted whatever address it resolves to.
- Do not add a port or scheme. An entry that is not a valid host name, address or range is ignored.
|
| Development > Webhooks - webhooks to internal addresses are refused, and Test and Resend require an administrator | Webhooks no longer post to internal addresses, and only an administrator can test or resend one.
- A webhook whose URL points to a loopback, private, link-local or other internal address, or to this server, is refused before it connects. Its delivery shows "Refused:" and the reason.
- To allow an internal endpoint, add it to
Master > Admin > Properties > Webhook Allowed Internal Hosts. A refused webhook retries every 10 minutes up to its Max Attempts, so adding the host in that time lets it deliver.
- Only http and https URLs are sent, and redirects are not followed. An endpoint that redirects, such as http to https, must be set to its final URL.
- Webhooks connect directly and ignore the server's proxy setting. A server with no direct internet access stops delivering webhooks.
- Send Test and Resend require the Admins role. LimitedAdmins users no longer see Resend, and Resend works only on this site's own webhooks.
Request Timeout now limits the whole request, including reading the response, to at most 30 seconds.
|
| Api > SystemSigning - the Master gives every website a signing key and endorses it | The Master now makes sure every website it hosts has a signing key, and vouches for each one with its own key.
- Websites whose folder path is not set in their website record are now included.
- A website that has never started gets its key from the Master.
- Approving the Master's key once also approves the keys of all its websites, so each website no longer needs its own approval before the old shared secret can be turned off.
- A website folder the Master cannot read is recorded once in the log, and the website's existing keys are still registered.
|
| Master > Admin > Settings - shows this server's signing key fingerprint | Master > Admin > Settings now shows this server's signing key fingerprint, so the Master's key can be confirmed without signing in to the server.
- Open the page and choose Page Options > Show/Hide Properties. The Signing Key Fingerprint row shows the server name and its fingerprint.
- Until the Master creates its key, the row reads "No key on this server yet."
- If the key file cannot be read, the page still loads and the row says so.
|
| Site-wide - the Uploads folder refuses backup, log, database and source files by URL (web.config change) | The Uploads folder and the PrivateLabeling folder now refuse .bak, .cs, .mdb, .accdb, .log and .sql files by URL. A request for one returns 404.
- Only
.accdb changes behavior. IIS serves it by default, so a file such as Uploads/MapDynamicRelationships/2Kubotas.accdb could be downloaded before.
- The other five extensions were already refused by IIS defaults. The rule now comes from your site's
web.config, so a client edit cannot drop it.
- Files stay on disk. Code that reads them from disk, including module views, is not affected.
- The next sync adds the rule to each site's Root
web.config. No other change is needed.
web.config change - read before you sync
- What changes: in the Root
web.config of each site and of the Master, the Uploads and PrivateLabeling locations each gain, for every extension above, <remove fileExtension="..." /> and <add fileExtension="..." allowed="false" />.
- Which files: the Root
web.config only. The deployment does not touch the Console web.config.
- Virtual directories that run as their own IIS application have a separate
web.config the deployment does not touch. If one serves files from Uploads by URL, add the same two entries to its web.config.
- Custom code or pages that link to a file with one of these extensions under
Uploads get a 404 after the sync. Move the file out of Uploads, or serve it through a page that reads it from disk.
- To check: open a virtual-directory site and a custom page that uses
Uploads links after the sync, and confirm both still load.
|
| Centralpoint Agent - Uploads data-file warnings skip files the site's web.config already refuses | Centralpoint Agent 8.12.16.21 stops reporting backup, log, database and source files under Uploads when the site's own web.config already refuses to serve them.
- The Agent reads the request-filtering rules in each site's Root
web.config. A file whose extension those rules deny is no longer counted.
- A group of files that is fully refused is not reported, and its open
SecurityDataFileExposed warning clears.
- Files under the Master's
Uploads/PrivateLabeling are still reported, because child sites serve that folder under their own web.config.
- A site with no readable Root
web.config is reported as before, and the check status names the site.
|