Ssl-certificate/en - История изменений

N.Bloshkin в 06:59, 5 июня 2024

2024-06-05T06:59:07Z

← Предыдущая версия		Версия от 09:59, 5 июня 2024
Строка 32:		Строка 32:
	* "Self-signed certificates" - Contact your company's IT department.		* "Self-signed certificates" - Contact your company's IT department.

	~~<div class="mw-translate-fuzzy">~~
	{\| class="wikitable"		{\| class="wikitable"
	\|+ Follow these guidelines from SmartPlayer for issuing certificates		\|+ Follow these guidelines from SmartPlayer for issuing certificates
Строка 44:		Строка 43:
	Reason for recommendation: A global certification authority trusted by all device manufacturers worldwide. The widest coverage of devices from manufacturers. SmartPlayer uses a certificate from this certification authority. For example, Samsung/LG - South Korea, BrightSign - UK, Android OS - countless different manufacturers, and they all trust GlobalSign.		Reason for recommendation: A global certification authority trusted by all device manufacturers worldwide. The widest coverage of devices from manufacturers. SmartPlayer uses a certificate from this certification authority. For example, Samsung/LG - South Korea, BrightSign - UK, Android OS - countless different manufacturers, and they all trust GlobalSign.
	\|-		\|-
	\|Do not use private certification authorities		\| Do not use private certification authorities
	Reason for recommendation: No device trusts private certification authorities. To launch https, you will need to add the certificate to the device's certificate store manually. And if there are more than 50 devices in the project? This already becomes a lot of routine manual work. The SmartPlayer platform does not yet support the loading of user certificates through the SmartPlayer personal account. This will be improved in the future, but there will not be a universal solution for all operating systems. There are manufacturer restrictions, for example, TizenOS does not provide an API for loading certificates as of May 30, 2024. Do not take unnecessary risks, use certificates from public certification authorities.}}		Reason for recommendation: No device trusts private certification authorities. To launch https, you will need to add the certificate to the device's certificate store manually. And if there are more than 50 devices in the project? This already becomes a lot of routine manual work. {{Note\|text=The SmartPlayer platform does not yet support the loading of user certificates through the SmartPlayer personal account. This will be improved in the future, but there will not be a universal solution for all operating systems. There are manufacturer restrictions, for example, TizenOS does not provide an API for loading certificates as of May 30, 2024. Do not take unnecessary risks, use certificates from public certification authorities.}}
	\|-		\|-
	\| Which type of certificate to choose?\|\| Reason for recommendation: Use DomainSSL (DV SSL). It is the cheapest and quickest to issue for ensuring work over the https protocol.		\| Which type of certificate to choose?\|\| Reason for recommendation: Use DomainSSL (DV SSL). It is the cheapest and quickest to issue for ensuring work over the https protocol.
	\|}		\|}
	~~</div>~~

	== '''Configuring the SmartPlayer Platform''' ==		== '''Configuring the SmartPlayer Platform''' ==

N.Bloshkin: Новая страница: «This does not affect the operation of the applications in any way; you can choose any option for hosting the platform.»

2024-06-05T06:51:59Z

Новая страница: «This does not affect the operation of the applications in any way; you can choose any option for hosting the platform.»

← Предыдущая версия		Версия от 09:51, 5 июня 2024
Строка 192:		Строка 192:
	# https://cms.smartplayer.org - личный кабинет		# https://cms.smartplayer.org - личный кабинет

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		This does not affect the operation of the applications in any way; you can choose any option for hosting the platform.
	~~На работу приложений это никак не влияет, можно выбрать любой вариант размещения платформы~~.
	~~</div>~~

N.Bloshkin: Новая страница: «Example of two domains for the personal account and server application: # https://api.smartplayer.org - серверное приложение # https://cms.smartplayer.org - личный кабинет»

2024-06-05T06:51:27Z

Новая страница: «Example of two domains for the personal account and server application: # https://api.smartplayer.org - серверное приложение # https://cms.smartplayer.org - личный кабинет»

← Предыдущая версия		Версия от 09:51, 5 июня 2024
Строка 188:		Строка 188:
	# https://develop.smartplayer.org/cms/ - personal account		# https://develop.smartplayer.org/cms/ - personal account

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		Example of two domains for the personal account and server application:
	~~Пример двух доменов для личного кабинета и серверного приложения~~:
	# https://api.smartplayer.org - серверное приложение		# https://api.smartplayer.org - серверное приложение
	# https://cms.smartplayer.org - личный кабинет		# https://cms.smartplayer.org - личный кабинет
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">
	На работу приложений это никак не влияет, можно выбрать любой вариант размещения платформы.		На работу приложений это никак не влияет, можно выбрать любой вариант размещения платформы.
	</div>		</div>

N.Bloshkin: Новая страница: «Example of a single domain for the personal account and server application: # https://develop.smartplayer.org - server application # https://develop.smartplayer.org/cms/ - personal account»

2024-06-05T06:50:39Z

Новая страница: «Example of a single domain for the personal account and server application: # https://develop.smartplayer.org - server application # https://develop.smartplayer.org/cms/ - personal account»

← Предыдущая версия		Версия от 09:50, 5 июня 2024
Строка 184:		Строка 184:
	=== If the server application and the personal account use the same domain, one certificate is sufficient. If different domains are used, two certificates need to be purchased. ===		=== If the server application and the personal account use the same domain, one certificate is sufficient. If different domains are used, two certificates need to be purchased. ===

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		Example of a single domain for the personal account and server application:
	~~Пример одного домена для личного кабинета и серверного приложения~~:		# https://develop.smartplayer.org - server application
	# https://develop.smartplayer.org - ~~серверное приложение~~		# https://develop.smartplayer.org/cms/ - personal account
	# https://develop.smartplayer.org/cms/ - ~~личный кабинет~~
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">

N.Bloshkin: Новая страница: «# The cost of the service is approximately 3000 rubles (includes the purchase of the certificate). Post-payment. The cost may vary, please check with the sales department. # The certificate will be valid for one year from the date of issuance. === If the server application and the personal account use the same domain, one certificate is sufficient. If different domains are used, two certificates need to be purchased. ===»

2024-06-05T06:49:52Z

Новая страница: «# The cost of the service is approximately 3000 rubles (includes the purchase of the certificate). Post-payment. The cost may vary, please check with the sales department. # The certificate will be valid for one year from the date of issuance. === If the server application and the personal account use the same domain, one certificate is sufficient. If different domains are used, two certificates need to be purchased. ===»

← Предыдущая версия		Версия от 09:49, 5 июня 2024
Строка 180:		Строка 180:
	\|}		\|}

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		# The cost of the service is approximately 3000 rubles (includes the purchase of the certificate). Post-payment. The cost may vary, please check with the sales department.
	# ~~Стоимость услуги примерно 3000р~~ (~~включает покупку сертификата~~). ~~Постоплата~~. ~~Стоимость может меняться~~, ~~уточняйте в отделе продаж~~.		# The certificate will be valid for one year from the date of issuance.
	# ~~Сертификат будет действовать - один год с момента выпуска~~.		=== If the server application and the personal account use the same domain, one certificate is sufficient. If different domains are used, two certificates need to be purchased. ===
	=== ~~Если серверное приложение и личный кабинет используют один домен~~, ~~то достаточно одного сертификата~~. ~~Если разные домены то нужно покупать 2 сертификата~~. ===
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">

N.Bloshkin: Новая страница: «{| class="wikitable" |+ Issuing a certificate using a SmartPlayer employee |- ! Step name !! Description of actions !! Responsible |- | Buy a GlobalSign certificate on the reg.ru website || Purchase a DomainSSL level certificate || SmartPlayer employee |- | Sending TXT record || A SmartPlayer employee will send the TXT record that needs to be added for the domain|| SmartPlayer employee - | Adding a TXT record for the domain || Add the TXT record for the doma...»

2024-06-05T06:49:09Z

Новая страница: «{| class="wikitable" |+ Issuing a certificate using a SmartPlayer employee |- ! Step name !! Description of actions !! Responsible |- | Buy a GlobalSign certificate on the reg.ru website || Purchase a DomainSSL level certificate || SmartPlayer employee |- | Sending TXT record || A SmartPlayer employee will send the TXT record that needs to be added for the domain|| SmartPlayer employee - | Adding a TXT record for the domain || Add the TXT record for the doma...»

← Предыдущая версия		Версия от 09:49, 5 июня 2024
Строка 164:		Строка 164:
	SmartPlayer can issue a certificate for a project, but this requires the participation of the domain administrator for which the certificate will be issued. To start the certificate issuance process, you need to obtain the domain name for which the certificate needs to be issued (for example, api.smartplayer.org/cms.smartplayer.org).		SmartPlayer can issue a certificate for a project, but this requires the participation of the domain administrator for which the certificate will be issued. To start the certificate issuance process, you need to obtain the domain name for which the certificate needs to be issued (for example, api.smartplayer.org/cms.smartplayer.org).

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~
	{\| class="wikitable"		{\| class="wikitable"
	\|+ ~~Выпуск сертификата с помощью сотрудника~~ SmartPlayer		\|+ Issuing a certificate using a SmartPlayer employee
	\|-		\|-
	! ~~Наименование шага~~ !! ~~Описание действий~~ !! ~~Ответственные~~		! Step name !! Description of actions !! Responsible
	\|-		\|-
	\| ~~Купить сертификат~~ GlobalSign ~~на сайте~~ reg.ru \|\| ~~Покупка сертификата уровня~~ DomainSSL \|\| ~~Сотрудник~~ SmartPlayer		\| Buy a GlobalSign certificate on the reg.ru website \|\| Purchase a DomainSSL level certificate \|\| SmartPlayer employee
	\|-		\|-
	\| ~~Отправка~~ TXT ~~записи~~ \|\| ~~Сотрудник~~ SmartPlayer ~~отправит~~ TXT ~~запись которую нужно будет добавить для домена~~ \|\| ~~Сотрудник~~ SmartPlayer		\| Sending TXT record \|\| A SmartPlayer employee will send the TXT record that needs to be added for the domain\|\| SmartPlayer employee
			-
			\| Adding a TXT record for the domain \|\| Add the TXT record for the domain \|\| Domain administrator (organization employee)
	\|-		\|-
	\| ~~Добавление TXT записи для домена~~ \|\| ~~Добавить TXT запись для домена~~ \|\| ~~Администратор домена (сотрудник организации)~~		\| Creating a certificate chain \|\| A certificate chain is created for installation on the server application\|\| SmartPlayer employee
	\|-		\|-
	\| Создание цепочки сертификатов \|\| Создается цепочка сертификатов для установки на серверном приложении \|\| Сотрудник SmartPlayer		\| Sending the archive (root certificate, certificate chain, private key) \|\| Sending the archive with certificate data \|\| SmartPlayer employee
	\|-
	~~\| Отправка архива с~~ (~~корневым сертификатов~~, ~~цепочкой сертификатов~~, ~~приватным ключом~~) \|\| ~~Отправка архива с данными по сертификату~~ \|\| ~~Сотрудник~~ SmartPlayer
	\|}		\|}
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">

N.Bloshkin: Новая страница: «= '''Certificate Issuance by SmartPlayer Employees''' = SmartPlayer can issue a certificate for a project, but this requires the participation of the domain administrator for which the certificate will be issued. To start the certificate issuance process, you need to obtain the domain name for which the certificate needs to be issued (for example, api.smartplayer.org/cms.smartplayer.org).»

2024-06-05T06:43:11Z

Новая страница: «= '''Certificate Issuance by SmartPlayer Employees''' = SmartPlayer can issue a certificate for a project, but this requires the participation of the domain administrator for which the certificate will be issued. To start the certificate issuance process, you need to obtain the domain name for which the certificate needs to be issued (for example, api.smartplayer.org/cms.smartplayer.org).»

← Предыдущая версия		Версия от 09:43, 5 июня 2024
Строка 161:		Строка 161:
	Now it is clear that the browser trusts our certificate signed by the private certification authority. If you need to test any client application, request a build on the server https://self-certificate-api.smartplayer.org/ for testing from the company's manager.		Now it is clear that the browser trusts our certificate signed by the private certification authority. If you need to test any client application, request a build on the server https://self-certificate-api.smartplayer.org/ for testing from the company's manager.

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		= '''Certificate Issuance by SmartPlayer Employees''' =
	= '''~~Выпуск сертификата сотрудниками~~ SmartPlayer''' =		SmartPlayer can issue a certificate for a project, but this requires the participation of the domain administrator for which the certificate will be issued. To start the certificate issuance process, you need to obtain the domain name for which the certificate needs to be issued (for example, api.smartplayer.org/cms.smartplayer.org).
	SmartPlayer ~~можем выпустить сертификат для проекта~~, ~~но для этого требуется участие администратора домена~~, на который будет выпущен сертификат. Для начала выпуска сертификата нужно получить название домена на который нужно выпускать сертификат (~~например~~ api.smartplayer.org/cms.smartplayer.org).
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">

N.Bloshkin: Новая страница: «Now it is clear that the browser trusts our certificate signed by the private certification authority. If you need to test any client application, request a build on the server https://self-certificate-api.smartplayer.org/ for testing from the company's manager.»

2024-06-05T06:41:58Z

Новая страница: «Now it is clear that the browser trusts our certificate signed by the private certification authority. If you need to test any client application, request a build on the server https://self-certificate-api.smartplayer.org/ for testing from the company's manager.»

← Предыдущая версия		Версия от 09:41, 5 июня 2024
Строка 159:		Строка 159:
	[[Файл:Screenshot from 2024-05-30 18-36-42.png\|безрамки\|центр]]		[[Файл:Screenshot from 2024-05-30 18-36-42.png\|безрамки\|центр]]

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		Now it is clear that the browser trusts our certificate signed by the private certification authority. If you need to test any client application, request a build on the server https://self-certificate-api.smartplayer.org/ for testing from the company's manager.
	~~Теперь видно, что браузер доверяет нашему сертификату, который подписан частным центром сертификации~~. ~~если нужно протестировать любое клиентское приложение~~, ~~запросите сборку его на сервер~~ https://self-certificate-api.smartplayer.org/ ~~для тестирования у менеджера компании~~.
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">

N.Bloshkin: Новая страница: «Personal area центр»

2024-06-05T06:41:19Z

Новая страница: «Personal area безрамки|центр»

← Предыдущая версия		Версия от 09:41, 5 июня 2024
Строка 156:		Строка 156:
	[[Файл:Screenshot from 2024-05-30 18-35-55.png\|безрамки\|центр]]		[[Файл:Screenshot from 2024-05-30 18-35-55.png\|безрамки\|центр]]

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		Personal area
	~~Личный кабинет~~
	[[Файл:Screenshot from 2024-05-30 18-36-42.png\|безрамки\|центр]]		[[Файл:Screenshot from 2024-05-30 18-36-42.png\|безрамки\|центр]]
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">

N.Bloshkin: Новая страница: «Server application центр»

2024-06-05T06:40:54Z

Новая страница: «Server application безрамки|центр»

← Предыдущая версия		Версия от 09:40, 5 июня 2024
Строка 153:		Строка 153:
	# https://self-certificate-api.smartplayer.org/		# https://self-certificate-api.smartplayer.org/

	~~<div lang="ru" dir="ltr" class="mw-content-ltr">~~		Server application
	~~Серверное приложение~~
	[[Файл:Screenshot from 2024-05-30 18-35-55.png\|безрамки\|центр]]		[[Файл:Screenshot from 2024-05-30 18-35-55.png\|безрамки\|центр]]
	~~</div>~~

	<div lang="ru" dir="ltr" class="mw-content-ltr">		<div lang="ru" dir="ltr" class="mw-content-ltr">