This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
IGEL OS 12 - No IGEL Properties
IGEL OS 12, created with OSC 12.03 and younger, does not provide IGEL-specific properties in deviceTRUST. Here’s why and how to fix.
Problem: No IGEL-specific deviceTRUST® properties are supplied by IGEL OS 12
Reason: IGEL has changed the file system rights starting with clients rolled out based on OSC 12.03. The folder “/wfs/igel-rmagent” can now only be read by root, no longer by other entities. deviceTRUST needs access to the folder in order to be able to read various properties. Our process recognizes the missing rights and ends the evaluation. Therefore, no IGEL-specific values are evaluated and shown in the session.
Workaround: A “custom command” for setting authorization provides a remedy. We have tested various scenarios and narrowed down the required rights so that a recursive “o+rx” (add read and execute for “others”) is sufficient: chmod -R o+rx /wfs/igel-rmagent.
We assume that the setting of the rights was no coincidence and are working on a solution to mitigate this behavior without requiring this workaround. Until then, please implement the workaround to make sure deviceTRUST can operate as desired.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.