Translations:SSO (версия для системного администратора)/9/en: различия между версиями

Материал из SmartPlayer
(Новая страница: «== '''Identified Setup Issues:''' == * '''Situation: The claim rules are set up incorrectly.<br> '''Solution:''' Claim rules must necessarily be set up in the same language. In our case, on the SmartPlayer server, the claim rules were written in Russian, while the client's were in English. On our side, it was written as "Адрес электронной почты" (Email Address), and for the client, it was "E-mail". Once the customer rewrote them in Russi...»)
 
Нет описания правки
 
Строка 1: Строка 1:
== '''Identified Setup Issues:''' ==
== '''Identified Setup Issues:''' ==
* '''Situation: The claim rules are set up incorrectly.<br>
* '''Situation: The claim rules are set up incorrectly.<br>
[[File:Claim rules .png|thumb|An example of the difference in filling "Claim Rules"|300px]]
'''Solution:''' Claim rules must necessarily be set up in the same language. In our case, on the SmartPlayer server, the claim rules were written in Russian, while the client's were in English. On our side, it was written as "Адрес электронной почты" (Email Address), and for the client, it was "E-mail". Once the customer rewrote them in Russian on their ADFS server, the problem was resolved.
'''Solution:''' Claim rules must necessarily be set up in the same language. In our case, on the SmartPlayer server, the claim rules were written in Russian, while the client's were in English. On our side, it was written as "Адрес электронной почты" (Email Address), and for the client, it was "E-mail". Once the customer rewrote them in Russian on their ADFS server, the problem was resolved.
* '''Situation:''' Incorrect certificate submission. <br>
* '''Situation:''' Incorrect certificate submission. <br>
'''Solution:'''  System administrators from the client side sent the certificate in text format, which turned out to be incorrect and inconvenient to use. After sending the certificate in file format, the issue was resolved.
'''Solution:'''  System administrators from the client side sent the certificate in text format, which turned out to be incorrect and inconvenient to use. After sending the certificate in file format, the issue was resolved.

Текущая версия от 15:38, 14 августа 2023

Информация о сообщении (править)
Это сообщение не имеет описания. Если вы знаете, где или как это сообщение используется, то можете помочь другим переводчикам, добавив к нему описание.
Определение сообщения (SSO (версия для системного администратора))
== '''Выявленные проблемы при настройке''' ==
* '''Ситуация:''' неправильно настроены claim rules.<br>
[[File:Claim rules .png|thumb|Пример разницы в заполнении "Claim Rules"|300px]]
'''Решение:''' Claim rules обязательно должны быть настроены на одном языке. В нашем случае на сервере SmartPlayer claim rules были прописаны на русском языке, а у клиента не английском. На нашей стороне было прописано "Адрес электронной почты", а у клиента "Е-mail". После того, как заказчик переписал их на своём ADFS сервере на русском, проблема решилась.
* '''Ситуация:''' некорректная отправка сертификатов. <br>
'''Решение:''' Системные администраторы со стороны заказчика отправили сертификат в виде текста, что оказалось некорректным и неудобным в использовании. После отправки сертификата в виде файла, ситуация была решена.

Identified Setup Issues:

  • Situation: The claim rules are set up incorrectly.
An example of the difference in filling "Claim Rules"

Solution: Claim rules must necessarily be set up in the same language. In our case, on the SmartPlayer server, the claim rules were written in Russian, while the client's were in English. On our side, it was written as "Адрес электронной почты" (Email Address), and for the client, it was "E-mail". Once the customer rewrote them in Russian on their ADFS server, the problem was resolved.

  • Situation: Incorrect certificate submission.

Solution: System administrators from the client side sent the certificate in text format, which turned out to be incorrect and inconvenient to use. After sending the certificate in file format, the issue was resolved.