Notice: Funksjonen _load_textdomain_just_in_time ble kalt feil. Innlasting av oversettelser for tekstdomenet twentytwelve ble utløst for tidlig. Dette er vanligvis en inikasjon på at noe kode i utvidelsen eller temaet kjører for tidlig. Oversettelser bør lastes inn med knaggen init eller senere. Se Feilsøking i WordPress for mer informasjon. (Denne meldingen ble lagt i versjon 6.7.0.) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php on line 6114 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6114) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1893 {"id":847,"date":"2021-08-24T15:12:29","date_gmt":"2021-08-24T13:12:29","guid":{"rendered":"https:\/\/vedaa.net\/?p=847"},"modified":"2021-08-27T10:53:04","modified_gmt":"2021-08-27T08:53:04","slug":"how-to-enable-true-sso-for-vrealize-suite-logins","status":"publish","type":"post","link":"https:\/\/vedaa.net\/vmware\/how-to-enable-true-sso-for-vrealize-suite-logins\/","title":{"rendered":"How to enable true SSO for vRealize suite logins"},"content":{"rendered":"\n

If you have vRealize Suite license it is a good chance that you have deployed a vRealize Suite Lifecycle Manager and the included Identity Manager appliance. If not you probably should! You will have a nice portal for all your vRealize URLs with SSO, but you do not have true SSO all the way from your windows client to your vRealize applications. Users still have to login to the portal each time they want to use it. Here is a quick write up on how to enable kerberos authentication to achieve true SSO.<\/p>\n\n\n\n

Attention<\/strong>
If you have vIDM 3.3.3 and 3.3.4 this feature is not working with the embedded connector. please upgrade to 3.3.5 where it is working again.<\/em><\/p>\n\n\n\n

In this blog I will walk you through how to setup true SSO, but first to some prerequisites.<\/p>\n\n\n\n

\"\"
vIDM portal<\/figcaption><\/figure>\n\n\n\n

Prerequisites<\/h3>\n\n\n\n