Skip to content

Commit 4b3e298

Browse files
concur-docs-machineconcur-docs-machine
committed
[skip ci] Updates
1 parent abf9c99 commit 4b3e298

File tree

2 files changed

+104
-2
lines changed

2 files changed

+104
-2
lines changed

‎feed.xml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
<description>Concur docs provides comprehensive information on working with the Concur platform</description>
66
<link>https://preview.developer.concur.com/</link>
77
<atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
8-
<pubDate>Tue, 14 Oct 2025 17:09:12 +0000</pubDate>
9-
<lastBuildDate>Tue, 14 Oct 2025 17:09:12 +0000</lastBuildDate>
8+
<pubDate>Thu, 16 Oct 2025 19:07:04 +0000</pubDate>
9+
<lastBuildDate>Thu, 16 Oct 2025 19:07:04 +0000</lastBuildDate>
1010
<generator>Jekyll v4.1.1</generator>
1111

1212
</channel>

‎tools-support/release-notes/api/2025-10-02.html‎

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -453,6 +453,108 @@ <h1 id="api-release-notes-october-2025">API Release Notes, October 2025</h1>
453453

454454
<h2 id="new-this-month">New This Month</h2>
455455

456+
<h3 id="now-available-hotel-service-v4-new-callback-url">Now Available: Hotel Service v4 New Callback URL</h3>
457+
458+
<p>The Change Notification API does not currently provide a way for the hotel connector to know which datacenter to use for the given booking. To resolve this we are adding a callback url to the Hotel Service v4 Reservation request (along with the trip/booking IDs that we are already adding today) based on whatever datacenter the service is running in.</p>
459+
460+
<p>New element added to the ReservationCriteria:</p>
461+
462+
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>"hrefs": {
463+
"changeNotificationV4": "https://us2.api.concursolutions.com/travel/v4/trips/{TRIP_ID}/hotels/change-notification",
464+
"authV0": "https://us2.api.concursolutions.com/oauth2/v0/token"
465+
}
466+
</code></pre></div></div>
467+
468+
<p>Note that {TRIP_ID} in above endpoint will be substituted with actual Trip ID used for the booking.</p>
469+
470+
<h3 id="now-available-hotel-service-v4-new-accepted-payments-response-field">Now Available: Hotel Service v4 New Accepted Payments Response Field</h3>
471+
472+
<p>A new field has been added to Hotel Service v4 Search response to allow suppliers to send us accepted payments. This will be used to populate a filter on the Search results page so that the user can filter for hotels that accept American Express, for example.</p>
473+
474+
<p>Accepted Payments should be an array of strings:</p>
475+
476+
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>"acceptedPayments": [
477+
"AMERICAN EXPRESS"
478+
]
479+
</code></pre></div></div>
480+
481+
<h3 id="preview-digital-certificates-to-be-transitioned-to-digicert-global-root-g2-and-g3-authorities">Preview: Digital Certificates to be Transitioned to DigiCert Global Root G2 and G3 Authorities</h3>
482+
483+
<p>The following change applies to the <strong>Concur Cloud for Public Sector</strong> data center: To maintain compliance with evolving security standards and ensure uninterrupted compatibility with Mozilla-based browsers, SAP Concur is transitioning our digital certificates to the following updated DigiCert Global Root G2 and G3 authorities:</p>
484+
485+
<ul>
486+
<li>DigiCert Global Root G2 – for RSA-based certificates</li>
487+
<li>DigiCert Global Root G3 – for ECDSA-based certificates</li>
488+
</ul>
489+
490+
<p>Adopting the new root certificates is critical to avoid potential trust errors or connection issues when accessing our services via Mozilla browsers.</p>
491+
492+
<blockquote>
493+
<p><strong>Note</strong>: This proactive update follows DigiCert’s announcement regarding Mozilla’s planned deprecation of the DigiCert Global Root CA.</p>
494+
</blockquote>
495+
496+
<ul>
497+
<li>Information First Published: October 10, 2025</li>
498+
<li>Applies to: All Products</li>
499+
<li>Applicable Data Centers: Concur Cloud for Public Sector</li>
500+
</ul>
501+
502+
<blockquote>
503+
<p><strong>Note</strong>: The information in this release note applies to the Concur Cloud for Public Sector data center. For information about Digital Certificate transitions for other data centers, refer to <a href="https://help.sap.com/docs/SAP_CONCUR/c5d6d15e7ecb4b4d8238b383d59ac2f4/1164714ddbd044c5aeca870bbc4e4a3a.html"><strong>Ongoing</strong> Digital Certificates to be Transitioned to DigiCert Global Root G2 and G3 Authorities</a> in the Release Notes section of these release notes.</p>
504+
</blockquote>
505+
506+
<table>
507+
<thead>
508+
<tr>
509+
<th>Edition</th>
510+
<th>Component</th>
511+
<th>Administrator Action</th>
512+
<th>Availability Target</th>
513+
</tr>
514+
</thead>
515+
<tbody>
516+
<tr>
517+
<td>Professional and Standard</td>
518+
<td>Digital Certificates</td>
519+
<td>Required</td>
520+
<td>Refer to Availability Target Details</td>
521+
</tr>
522+
</tbody>
523+
</table>
524+
525+
<p><strong>Availability Target Details</strong>: SAP Concur plans to implement the changes on the following schedule:</p>
526+
527+
<p><strong>Target Implementation Dates</strong></p>
528+
529+
<table>
530+
<thead>
531+
<tr>
532+
<th>Certificate</th>
533+
<th>Implementation Date and Time</th>
534+
</tr>
535+
</thead>
536+
<tbody>
537+
<tr>
538+
<td>usg.concursolutions.com</td>
539+
<td>January 15, 2026 at 22:00 PDT</td>
540+
</tr>
541+
<tr>
542+
<td>usg.api.concursolutions.com</td>
543+
<td>January 22, 2026 at 22:00 PDT</td>
544+
</tr>
545+
</tbody>
546+
</table>
547+
548+
<p>Clients who have not pinned the certificate do not need to take any action as their certificate will be updated automatically. <strong>Most clients do not pin the certificate.</strong></p>
549+
550+
<blockquote>
551+
<p><strong>Note</strong>: Certificate pinning is not recommended. To maintain compliance with evolving security standards, SAP Concur renews certificates on a regular basis. Pinned certificates are <strong>not</strong> updated automatically and failure to manually update them before the implementation date might cause service disruptions.</p>
552+
</blockquote>
553+
554+
<blockquote>
555+
<p><strong>Note</strong>: SAP ICS customers who follow the certificate handling processes described in the following note do not need to take any action: <a href="https://help.sap.com/docs/SAP_CONCUR/c5d6d15e7ecb4b4d8238b383d59ac2f4/1164714ddbd044c5aeca870bbc4e4a3a.html">2914977 - FAQ: Concur Certificates, Authentication, and Connectivity</a>.</p>
556+
</blockquote>
557+
456558
<h3 id="updated-preview-new-client-ssl-certificate-for-ess-webhookapiconcursolutionscom">Updated Preview: New Client SSL Certificate for ESS webhook.api.concursolutions.com</h3>
457559

458560
<p><strong>Overview</strong></p>

0 commit comments

Comments
 (0)