home.social

#phs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #phs, aggregated by home.social.

  1. #アステル東京#おでかけ電話 コンセプトが最初から破綻していたっぽいことを知って笑っています #PHS #ASTEL #アステル

    "世界の動向を見るとエリアを離散的にポイントとして打ったシステムは失敗しており,ある面を連続的に打ったシステムが成功している"
    2. ネットワーク jstage.jst.go.jp/article/itej1 .

  2. Agir en « guerrier grec »? Noga Mishliborsky met en perspective l’engagement d’intellectuels au cours du XXème siècle avec leurs analyses académiques.

    Gagnez un exemplaire du volume nr. 129 de notre collection « Pariser Historische Studien » en partageant ce post ! 🎁

    Découvrez l'ouvrage : dhi-paris.fr/fr/actualites/pag

    Conditions de participation: ow.ly/ajni50HXpgB 🧐

    #Marx #Winckelmann #PHS #Antiquité #Tragédie #Philologie #Philosophie #Anthropologie #Antike #WWII #Histodons @histodons

  3. #Password #expiration for accounts no longer makes sense and is not recommended if multi-factor authentication (#MFA) is used. For this reason, it is recommended to disable password expiration in the #Microsoft365 environment as well.

    But what if the company has synchronized identities in the Password Hash Sync (#PHS) scenario? In that case, the #AzureAD password expiration policy is not applied to the synchronized accounts. And such accounts passwords are always set to never expire. It is assumed that in such a case the policy in Active Directory handles this.

    But what if the user never authenticates to the local AD? The computer has Azure AD Join and the user is only using cloud services. The password for his AD account has expired, but he doesn't even know about it, and Azure AD still authenticates the user because passwords for synchronized accounts never expire.

    In this case, you need to configure the Azure AD Connect server to apply the Azure AD password expiration policy also to synchronized accounts. This can be done using PowerShell on the Azure AD Connect server: Set-MsolDirSyncFeature -Feature EnforceCloudPasswordPolicyForPasswordSyncedUsers