diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 0000000000..b2a811c322 --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,16 @@ +# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates + +version: 2 +updates: + - package-ecosystem: "bundler" + directory: "/" + schedule: + interval: "weekly" + - package-ecosystem: "docker" + directory: "/" + schedule: + interval: "weekly" + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "weekly" diff --git a/Gemfile.lock b/Gemfile.lock index 4f47f93aa0..743c99fb64 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,7 +1,7 @@ GEM remote: https://rubygems.org/ specs: - activesupport (5.2.6) + activesupport (5.2.8) concurrent-ruby (~> 1.0, >= 1.0.2) i18n (>= 0.7, < 2) minitest (~> 5.1) @@ -14,25 +14,25 @@ GEM algoliasearch (1.27.5) httpclient (~> 2.8, >= 2.8.3) json (>= 1.5.1) - autoprefixer-rails (9.8.6) - execjs + autoprefixer-rails (10.4.7.0) + execjs (~> 2) chronic (0.10.2) colorator (1.1.0) - concurrent-ruby (1.1.9) - em-websocket (0.5.2) + concurrent-ruby (1.1.10) + em-websocket (0.5.3) eventmachine (>= 0.12.9) - http_parser.rb (~> 0.6.0) - ethon (0.14.0) + http_parser.rb (~> 0) + ethon (0.15.0) ffi (>= 1.15.0) eventmachine (1.2.7) execjs (2.8.1) extras (0.3.0) forwardable-extended (~> 2.5) - fastimage (2.2.5) - ffi (1.15.3) + fastimage (2.2.6) + ffi (1.15.5) filesize (0.2.0) forwardable-extended (2.6.0) - html-proofer (3.16.0) + html-proofer (3.19.1) addressable (~> 2.3) mercenary (~> 0.3) nokogumbo (~> 2.0) @@ -40,7 +40,7 @@ GEM rainbow (~> 3.0) typhoeus (~> 1.3) yell (~> 2.0) - http_parser.rb (0.6.0) + http_parser.rb (0.8.0) httpclient (2.8.3) i18n (0.9.5) concurrent-ruby (~> 1.0) @@ -77,11 +77,11 @@ GEM nokogiri (~> 1.8) pathutil (~> 0.16) sprockets (>= 3.3, < 4.1.beta) - jekyll-feed (0.13.0) + jekyll-feed (0.16.0) jekyll (>= 3.7, < 5.0) jekyll-gzip (2.5.1) jekyll (>= 3.0, < 5.0) - jekyll-redirect-from (0.15.0) + jekyll-redirect-from (0.16.0) jekyll (>= 3.3, < 5.0) jekyll-sanity (1.6.0) jekyll (>= 3.1, < 5.0) @@ -92,33 +92,37 @@ GEM jekyll (>= 3.7, < 5.0) jekyll-watch (2.2.1) listen (~> 3.0) - json (2.5.1) + json (2.6.2) kramdown (1.17.0) liquid (4.0.3) liquid-tag-parser (1.9.0) extras (~> 0.3) liquid (>= 3.0, < 5.0) - listen (3.5.0) + listen (3.7.1) rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) mercenary (0.3.6) - mini_portile2 (2.4.0) - minitest (5.14.4) - nokogiri (1.10.10) - mini_portile2 (~> 2.4.0) + mini_portile2 (2.6.1) + minitest (5.15.0) + nokogiri (1.12.5) + mini_portile2 (~> 2.6.1) + racc (~> 1.4) + nokogiri (1.12.5-x86_64-darwin) + racc (~> 1.4) nokogumbo (2.0.5) nokogiri (~> 1.8, >= 1.8.4) - parallel (1.19.2) + parallel (1.22.1) pathutil (0.16.2) forwardable-extended (~> 2.6) progressbar (1.11.0) - public_suffix (4.0.6) - rack (2.2.3) - rainbow (3.0.0) - rb-fsevent (0.11.0) + public_suffix (4.0.7) + racc (1.6.0) + rack (2.2.4) + rainbow (3.1.1) + rb-fsevent (0.11.1) rb-inotify (0.10.1) ffi (~> 1.0) - rouge (3.26.0) + rouge (3.29.0) safe_yaml (1.0.5) sass (3.7.4) sass-listen (~> 4.0.0) diff --git a/README.md b/README.md index 8400867af8..11682805c3 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ File name rules: Folder name rules: 1. They must be TitleCase -2. All files in the folder, must include a reference in its header to its folder name. This will be in either the documentname, categoryname, or subfoldername ( depending on the location of the folder) +2. All files in the folder, must include a reference in its header to its folder name. This will be in either the documentname, categoryname, or subfoldername (depending on the location of the folder) 3. All special characters excluding periods, dashes, and & need to be removed from Foldername 4. Periods are replaced with dashes. diff --git a/_data/releasenotesios.yaml b/_data/releasenotesios.yaml index 362892cf6c..d929784f38 100644 --- a/_data/releasenotesios.yaml +++ b/_data/releasenotesios.yaml @@ -12,6 +12,7 @@ Additional: #Limited Release Limited: versions: [ + { version: "6.8.3" }, { version: "6.8.2" }, { version: "6.8.1" }, { version: "6.7.1" }, diff --git a/_data/reportbuilder.yaml b/_data/reportbuilder.yaml index eaf3cd060b..cc762e128c 100644 --- a/_data/reportbuilder.yaml +++ b/_data/reportbuilder.yaml @@ -915,7 +915,7 @@ AnalysisType: "Campaign Conversions" Channel: Messaging Dashboard: "Business Activity for Messaging" - Description: "The percentage (%) of the total Conversations that may not have otherwise occured (Incremental Conversion ( calculated at the Brand Level)" + Description: "The percentage (%) of the total Conversations that may not have otherwise occured (Incremental Conversion (calculated at the Brand Level)" FormulaOptional: "INCREMENTAL CONVERSIONS (BRAND) / TOTAL CONVERSIONS AFTER ENGAGEMENT" Metric: "INCREMENTAL CONVERSION RATIO (BRAND)" filteredBy: "Date, Initial Device, Goal Type, Group , Source Type" @@ -5739,7 +5739,7 @@ AnalysisType: "Agent Survey" Channel: Messaging Dashboard: "Survey for Messaging" - Description: "The percentage (%) of submitted survey forms ( partial or complete) out of the number of opened survey forms" + Description: "The percentage (%) of submitted survey forms (partial or complete) out of the number of opened survey forms" FormulaOptional: "SUBMITTED AGENT SURVEY / OFFERED AGENT SURVEYS" Metric: "SUBMISSION RATE" filteredBy: "Agent, Group,Skill" diff --git a/_exclude/getting-started.md b/_exclude/getting-started.md index e4b9447478..61248bd45b 100644 --- a/_exclude/getting-started.md +++ b/_exclude/getting-started.md @@ -529,7 +529,7 @@ In this step, you set up an "escalation" to transfer the user to a human agent i -5. Add an [Agent Transfer interaction](conversation-builder-interactions-integrations.html#agent-transfer-interactions) ( ) beneath the Dialog Starter interaction. +5. Add an [Agent Transfer interaction](conversation-builder-interactions-integrations.html#agent-transfer-interactions) () beneath the Dialog Starter interaction. 6. Note the default message to be sent to the user prior to escalation. Replace this with, "Hold on while I transfer you to an agent..." Alternatively, if you don't want to send a message, enter "BLANK_MESSAGE". diff --git a/assets/Code examples/APIs/Engagement History API/Java-TranscriptSendEmail/pom.xml b/assets/Code examples/APIs/Engagement History API/Java-TranscriptSendEmail/pom.xml index 05be65e2b5..f9dfeeb43f 100644 --- a/assets/Code examples/APIs/Engagement History API/Java-TranscriptSendEmail/pom.xml +++ b/assets/Code examples/APIs/Engagement History API/Java-TranscriptSendEmail/pom.xml @@ -22,7 +22,7 @@ org.jsoup jsoup - 1.7.2 + 1.14.2 \ No newline at end of file diff --git a/package-lock.json b/package-lock.json index 764e83e209..664152e4a3 100644 --- a/package-lock.json +++ b/package-lock.json @@ -4760,9 +4760,9 @@ } }, "yargs-parser": { - "version": "21.0.0", - "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.0.0.tgz", - "integrity": "sha512-z9kApYUOCwoeZ78rfRYYWdiU/iNL6mwwYlkkZfJoyMR1xps+NEBX5X7XmRpxkZHhXJ6+Ey00IwKxBBSW9FIjyA==" + "version": "21.0.1", + "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.0.1.tgz", + "integrity": "sha512-9BK1jFpLzJROCI5TzwZL/TU4gqjK5xiHV/RfWLOahrjAko/e4DJkRDZQXfvqAsiZzzYhgAzbgz6lg48jcm4GLg==" }, "yeast": { "version": "0.1.2", diff --git a/package.json b/package.json index 380803335a..52d57e27ff 100644 --- a/package.json +++ b/package.json @@ -15,7 +15,7 @@ "lodash.template": ">=4.5.0", "object-path": ">=0.11.5", "socket.io": ">=2.4.0", - "yargs-parser": ">=13.1.2" + "yargs-parser": ">=21.0.1" }, "devDependencies": { "pre-commit": "^1.2.2" diff --git a/pages/Documents/ClientSideConfiguration/EngagementWindowWidgetSDK/Instructions/configuration.md b/pages/Documents/ClientSideConfiguration/EngagementWindowWidgetSDK/Instructions/configuration.md index 152bca0f7c..7e14f2f854 100644 --- a/pages/Documents/ClientSideConfiguration/EngagementWindowWidgetSDK/Instructions/configuration.md +++ b/pages/Documents/ClientSideConfiguration/EngagementWindowWidgetSDK/Instructions/configuration.md @@ -19,6 +19,6 @@ Widget is configured by the LivePerson account team based on the following prope - Show Refresh Button (True/False) - Widget URL (must be over https) - Widget Name (unique) - - Widget Start State ( OFFLINE / PRE_CONVERSATION / PENDING / ACCEPTED(chat only) / IN_QUEUE(messaging only) / INTERACTIVE / POST_CONVERSATION / ENDED ) + - Widget Start State (OFFLINE / PRE_CONVERSATION / PENDING / ACCEPTED(chat only) / IN_QUEUE(messaging only) / INTERACTIVE / POST_CONVERSATION / ENDED) - Messaging {enable: True/False, authenticated:True/False, unauthenticated:True/False} - Chat {enable: True/False, authenticated:True/False, unauthenticated:True/False} diff --git a/pages/Documents/ConversationalAI/ConversationBuilder/Integrations/troubleshooting.md b/pages/Documents/ConversationalAI/ConversationBuilder/Integrations/troubleshooting.md index f2fb7c9610..688378cbe7 100644 --- a/pages/Documents/ConversationalAI/ConversationBuilder/Integrations/troubleshooting.md +++ b/pages/Documents/ConversationalAI/ConversationBuilder/Integrations/troubleshooting.md @@ -17,7 +17,7 @@ Use this page to help you troubleshoot common issues when working with integrati #### New lines stored in variables -One issue that commonly occurs (on mobile phones in particular) is that the consumer adds a new line to their message, that new line ( \\n ) is stored as a part of a variable, and the variable is subsequently used in an integration, causing it to fail. +One issue that commonly occurs (on mobile phones in particular) is that the consumer adds a new line to their message, that new line (\\n) is stored as a part of a variable, and the variable is subsequently used in an integration, causing it to fail. For example, if the consumer's address is stored in a variable as "123 Main Street \n New York, New York 12345," and the variable is used in an integration, the integration will fail. This is by design to help to prevent injection attacks in the API. diff --git a/pages/Documents/MessagingChannels/AppleBusinessChatSDK/overview.md b/pages/Documents/MessagingChannels/AppleBusinessChatSDK/overview.md index 8811f9799f..30322aa43c 100644 --- a/pages/Documents/MessagingChannels/AppleBusinessChatSDK/overview.md +++ b/pages/Documents/MessagingChannels/AppleBusinessChatSDK/overview.md @@ -25,7 +25,7 @@ After sending a [Custom Interactive Message (CIM)](apple-business-chat-templates - Provides human and bot agents with context of the consumer’s iMessage app transactional and activity data, allowing them to have a more meaningful and effective conversation - Notify the developer of conversational events so that they can take action with custom SDEs - Create data-driven integrations to external systems via the agent widget SDK -- Provide out of the box UI Solutions incuding PCI compliant secure forms +- Provide out of the box UI Solutions including PCI compliant secure forms ### Who is the SDK for? @@ -41,9 +41,9 @@ The SDK has 2 distinctive contextual integration environments: #### Consumer Transaction over iMessage App 1. Consumer is messaging an appliance brand via Business Chat -2. Consumer is asking the agent to provide details on the delivery and installation offering for the their ovens. -3. Agent gives the consumer all the details on the delivery and installation, and consumer decides to buy both the oven and the delivery package. -4. Agent sends the consumer an iMessage app interaction that includes all products selected in cart area, with payment flow. +2. Consumer is asking the agent to provide details on the delivery and installation offering for their ovens. +3. Agent gives the consumer all the details on the delivery and installation, and the consumer decides to buy both the oven and the delivery package. +4. Agent sends the consumer an iMessage app interaction that includes all products selected in the cart area, with payment flow. Path A: diff --git a/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/ReleaseNotes/Limited/6.8.3.md b/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/ReleaseNotes/Limited/6.8.3.md new file mode 100644 index 0000000000..f52704202f --- /dev/null +++ b/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/ReleaseNotes/Limited/6.8.3.md @@ -0,0 +1,44 @@ +### Version 6.8.3 +#### iOS Messaging SDK + +**Release Date**: July 1st, 2022 + +##### Environmental Requirements +The iOS Mobile Messaging SDK version 6.8.3.838 is supported on iOS versions 13 through 15. + +**This XCFramework was compiled with Swift version Apple Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53) which means it will work Swift version 5.2.4 and above.** + +{: .notice} +XCFramework is supported on CocoaPad versions 1.9.0 and greater. + +##### New Features + +##### Exposing new Notification to be trigger once the Conversation Screen gets dismissed + +Create new Notification to be sent once the Conversation Screen is dismissed, this will work the same way as the LPMessagingSDKConversationViewControllerDidDismiss delegate. + +How to use: + +```swift +NotificationCenter.default.addObserver(self, + selector: #selector(lpMessagingSDKConversationViewControllerDidDismissedNotification), + name: Notification.Name("LP_CONVERSATION_VIEW_CONTROLLER_DISMISSED"), + object: nil) +``` + +> *lpMessagingSDKConversationViewControllerDidDismissedNotification* is a generic name for the function responding to the event + + +##### Enhancements + +- BrandName/AgentName will be announced as headers by VoiceOver assistant instead of text. + + +##### Bugs fixed + +- Fixed the issue with duplicated rendering of quick reply actions +- Fixed issue when Attachment Menu will be announced with wrong state, for modifying the default announcements, override the following keys: + - **fileSharingAttachmentMenu**: "Attachment menu" + - **fileSharingCloseAttachmentMenu**: "Close attachment menu" + +> For more information about localizing strings, see [link](mobile-app-messaging-sdk-for-ios-string-localization-localization-keys.html) \ No newline at end of file diff --git a/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/StringLocalization/localization-keys.md b/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/StringLocalization/localization-keys.md index 23498aa7a3..60953b3fa1 100644 --- a/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/StringLocalization/localization-keys.md +++ b/pages/Documents/MessagingChannels/MobileAppMessagingSDKforiOS/StringLocalization/localization-keys.md @@ -78,6 +78,8 @@ Localized keys with the English localization string. | facetimeAudio | "FaceTime Audio" | | feedbackNoButtonTitle | "No" | | feedbackYesButtonTitle | "Yes" | +| fileSharingAttachmentMenu | "Attachment menu" | +| fileSharingCloseAttachmentMenu | "Close attachment menu" | | fileSharingDocument | "Document" | | fileSharingFileSizeLimitation | "File size exceeds the %d MB limitation" | | fileSharingSendFile | "Send File" | diff --git a/pages/Documents/Reporting/DataAccessAPI/changelog.md b/pages/Documents/Reporting/DataAccessAPI/changelog.md index c3982632f6..2445298b57 100644 --- a/pages/Documents/Reporting/DataAccessAPI/changelog.md +++ b/pages/Documents/Reporting/DataAccessAPI/changelog.md @@ -30,7 +30,7 @@ All future dates found in this documentation reflect approximations for upcoming 2. Scan for files according to the request's parameters (reduce probability of timeout). -3. In Web Session, add to impression section controlGroup field ( a new field that will be added to the schema - version 1.0.0.35) +3. In Web Session, add to impression section controlGroup field (a new field that will be added to the schema - version 1.0.0.35) ### June 18th, 2017 diff --git a/pages/Documents/Reporting/MessagingOperationsAPI/Methods/messaging-estimated-wait-time.md b/pages/Documents/Reporting/MessagingOperationsAPI/Methods/messaging-estimated-wait-time.md index 21a07e9f96..a33bb59635 100644 --- a/pages/Documents/Reporting/MessagingOperationsAPI/Methods/messaging-estimated-wait-time.md +++ b/pages/Documents/Reporting/MessagingOperationsAPI/Methods/messaging-estimated-wait-time.md @@ -41,7 +41,7 @@ This method returns the current average wait time in queue, per requested skill. | Name | Description | Type / Value | Required | | :----- | :-------------- | :-------------- | :--- | | v | version of API e.g. v=1 | numeric | default: 1 | -| skills | When provided, the response will contain estimated wait time data for the requested skill Id/s. When not provided, the response will contain estimated wait time data for all skills of the account. If there is no data for the specified skill/s an object will be returned with value -1 for key: "ewt". You can provide one or more skill Ids. If you provide several skill IDs, they must be comma separated. Example: skills=4,15,3. | numeric, separated by commas | optional | +| skills | When provided, the response will contain estimated wait time data for the requested skill Id/s. When not provided, the response will contain estimated wait time data for all skills of the account. If there is no data for the specified skill/s an object will be returned with value -1 for key: "estimatedWaitTime". You can provide one or more skill Ids. If you provide several skill IDs, they must be comma-separated. Example: skills=4,15,3. | numeric, separated by commas | optional | **Response Body** diff --git a/pages/Documents/RichMessaging/AppleMessagesForBusinessTemplates/custom-interactive-message-template.md b/pages/Documents/RichMessaging/AppleMessagesForBusinessTemplates/custom-interactive-message-template.md index 786de49e7a..06beb60eb8 100644 --- a/pages/Documents/RichMessaging/AppleMessagesForBusinessTemplates/custom-interactive-message-template.md +++ b/pages/Documents/RichMessaging/AppleMessagesForBusinessTemplates/custom-interactive-message-template.md @@ -12,7 +12,7 @@ indicator: messaging The Custom Interactive Message (CIM) Template for App Business Chat allows you to invoke an iOS iMessage app / extension on the consumer device. This app can allow for a wide range of interactivity without requiring the consumer to leave the conversation. -Sending the structured content templates (body and metadata) explained in this document will allow you to send the iMessage app / extension to the consumer device. +Sending the structured content templates (body and metadata) explained in this document will allow you to send the iMessage app / extension to the consumer device. For how to create an iMessage app / extension, see the Apple documentation [here](https://developer.apple.com/imessage/). @@ -154,13 +154,13 @@ Using Metadata, you can also control the visual appearance of the bubble that di ```json [{ - "type": "BusinessChatCustomMessage", - "appId": 1234, - "appName": "productselection", - "bid": "com.apple.messages.MSMessageExtensionBalloonPlugin:yourTEAMID:yourextensionbundleID", - "sessionIdentifier": "", - "useLiveLayout": true, - "receivedMessage": { + "type": "BusinessChatCustomMessage", + "appId": 1234, + "appName": "productselection", + "bid": "com.apple.messages.MSMessageExtensionBalloonPlugin:yourTEAMID:yourextensionbundleID", + "sessionIdentifier": "", + "useLiveLayout": true, + "receivedMessage": { "imageURL":"https://s3.amazonaws.com/lp-mobile-apps/WelcomeMessagePOC/Welcome-02-web-version.jpg", "title": "Welcome!", "style": "icon", @@ -169,8 +169,8 @@ Using Metadata, you can also control the visual appearance of the bubble that di "tertiarySubtitle": "", "imageTitle": "", "imageSubtitle": "" - }, - "URL": "” + }, + "URL": "” }] ``` @@ -180,23 +180,23 @@ The value of the `URL` metadata property will be passed to Apple's [MSMessage](h #### Metadata Guidelines -* General recommendation for the URL field is to use an URI encoded data object which will represent the URL +* General recommendation for the URL field is to use an URI encoded data object which will represent the URL -* Please note! The URL should be lean as possible as described in the example above, and should not replace or attempt to act as the app model. +* Please note! The URL should be lean as possible as described in the example above, and should not replace or attempt to act as the app model. -* The AppID, Extension Bundle ID and Team ID (which are part of the Bid field) must be part of the SC metadata JSON! Without them your iMessage app will not be delivered to the consumer. +* The AppID, Extension Bundle ID and Team ID (which are part of the Bid field) must be part of the SC metadata JSON! Without them your iMessage app will not be delivered to the consumer. -* RecivedBubble image URL - If consumer does not have the extension installed on device, or if consumer has the extension installed but does not use LiveLayout (set to false) then the recivedBubble will default to the imageURL set in the recievedBubble object. If imageURL was not added to the SC schema defined, the layout view will be an empty frame! Always include an imageURL! +* RecivedBubble image URL - If consumer does not have the extension installed on device, or if consumer has the extension installed but does not use LiveLayout (set to false) then the recivedBubble will default to the imageURL set in the recievedBubble object. If imageURL was not added to the SC schema defined, the layout view will be an empty frame! Always include an imageURL! * ImageURL MUST be whitelisted - to whitelist images for Structured Content contact your Conversational Cloud account representative -* SessionIdentifier - Any interactive message that is sent to ABC has a UUID - either you can set it through this field, or if not set Apple will generate a UUID for the interactive message. We recommend you set the UUID for each interactive message sent from the agent, in order to maintain referencing and correlating between interactions, for grouping messages, funnel tags and more. +* SessionIdentifier - Any interactive message that is sent to ABC has a UUID - either you can set it through this field, or if not set Apple will generate a UUID for the interactive message. We recommend you set the UUID for each interactive message sent from the agent, in order to maintain referencing and correlating between interactions, for grouping messages, funnel tags and more. * Images placed in the image used in imageURL field should be whitelisted in account Houston - Site Setting messaging.rich.content.valid.urls * When no app exists on the receiving device that can consume the message, if this URL is a HTTP(S) url, it will be loaded in a web browser. -* The root object of the JSON in the URL field should be a dictionary (key:value) and not an array ( {} and not [] ). +* The root object of the JSON in the URL field should be a dictionary (key:value) and not an array ({} and not []). #### Metadata Limitations @@ -233,7 +233,7 @@ In order to do this, all code is handled from within your Apple iMessage app / e 3. Create a URL by adding the encoded JSON on a query parameter `data` like the following: `?data=` -4. Set the [url](https://developer.apple.com/documentation/messages/msmessage/1649739-url) property of the [MSMessage](https://developer.apple.com/documentation/messages/msmessage) object to the URL that you constructed. +4. Set the [url](https://developer.apple.com/documentation/messages/msmessage/1649739-url) property of the [MSMessage](https://developer.apple.com/documentation/messages/msmessage) object to the URL that you constructed. 5. [Send](https://developer.apple.com/documentation/messages/msconversation/2909036-send) the MSMessage object from your iMessage app / extension. diff --git a/pages/Documents/Security&Authentication/ConsumerAuthentication/detailed-api.md b/pages/Documents/Security&Authentication/ConsumerAuthentication/detailed-api.md index 38e1541e56..c3b41f8c15 100644 --- a/pages/Documents/Security&Authentication/ConsumerAuthentication/detailed-api.md +++ b/pages/Documents/Security&Authentication/ConsumerAuthentication/detailed-api.md @@ -206,7 +206,7 @@ LivePerson supports the following claims set, which will be displayed to the age |email |End-User's preferred e-mail address. Its value MUST conform to the RFC 5322 [RFC5322] addr-spec syntax. The RP MUST NOT rely upon this value being unique, as discussed in Section 5.7.|string| Personal info (including Email address)| Personalinfo.personalcontact.email| |gender |End-user's gender. Values defined by this specification are female and male. Other values MAY be used when neither of the defined values are applicable|string| Personal info (including Gender)| Personalinfo.gender| |preferred_username |Shorthand name by which the end-user wishes to be referred by at the RP such as janedoe or j.doe. This value MAY be any valid JSON string including special characters such as @, /, or whitespace. The RP MUST NOT rely upon this value being unique.|string| Consumer info (including User Name)| CustomerInfo.username| -|phone_number |End-user's preferred telephone number. E.164 [E.164] is RECOMMENDED as the format of this Claim, for example, +1 (425) 555-1212 or +56 (2) 687 2400. If the phone number contains an extension, it is recommended that the extension be represented using the RFC 3966 [RFC3966] extension syntax, for example, +1 (604) 555-1234;ext=5678.|string| Personal info (including Phone number)| PersonalInfo.contacts[].phone| +|phone_number |End-user's preferred telephone number. E.164 [E.164] is RECOMMENDED as the format of this Claim, for example, +1 (425) 555-1212 or +56 (2) 687 2400. If the phone number contains an extension, it is recommended that the extension be represented using the RFC 3966 [RFC3966] extension syntax, for example, +1 (604) 555-1234;ext=5678.|string| Consumer info (including IMEI)| CustomerInfo.imei| **Example for Mandatory+Standard Claims JWT**: @@ -333,7 +333,7 @@ openssl rsa -in private_idp.pem -outform PEM -pubout -out public_key_idp.pem **Configure the JWT public key on Conversational Cloud UI:** -1. Remove the header and tail ( "-----BEGIN PUBLIC KEY-----" & "-----END PUBLIC KEY-----" ) +1. Remove the header and tail ("-----BEGIN PUBLIC KEY-----" & "-----END PUBLIC KEY-----") Example: diff --git a/pages/Documents/Security&Authentication/ConsumerDelegation/configuration.md b/pages/Documents/Security&Authentication/ConsumerDelegation/configuration.md index a149aa4286..79895b14d7 100644 --- a/pages/Documents/Security&Authentication/ConsumerDelegation/configuration.md +++ b/pages/Documents/Security&Authentication/ConsumerDelegation/configuration.md @@ -20,7 +20,7 @@ Only the following parameters should be defined: * OAuth 2.0 Client Secret -* JWT Public Key - Set feild value to: "CONSUMER_DELEGATION" +* JWT Public Key - Set field value to: "CONSUMER_DELEGATION" To define the OAuth 2.0 delegation: diff --git a/pages/Documents/Security&Authentication/MTLS/Methods/get-all-certificates-by-account.md b/pages/Documents/Security&Authentication/MTLS/Methods/get-all-certificates-by-account.md index 8694a4b236..8c6d14e4b9 100644 --- a/pages/Documents/Security&Authentication/MTLS/Methods/get-all-certificates-by-account.md +++ b/pages/Documents/Security&Authentication/MTLS/Methods/get-all-certificates-by-account.md @@ -23,7 +23,6 @@ This API gets all certificates from a specific account by account ID. |:------| :-------- | |Authorization| Contains token string to allow request authentication and authorization. | -**Request Body** **Path Parameters**