Deprecated: Funksjonen jetpack_form_register_pattern er foreldet siden versjon jetpack-13.4! Bruk Automattic\Jetpack\Forms\ContactForm\Util::register_pattern i stedet. in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php on line 6078 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 {"id":263,"date":"2019-11-26T14:10:47","date_gmt":"2019-11-26T13:10:47","guid":{"rendered":"https:\/\/vedaa.net\/?p=263"},"modified":"2019-11-26T14:10:54","modified_gmt":"2019-11-26T13:10:54","slug":"how-to-configure-sso-web-links-in-vmware-identity-manager-catalog-for-vrealize-suite-lifecycle-manager-imported-products","status":"publish","type":"post","link":"https:\/\/vedaa.net\/vmware\/how-to-configure-sso-web-links-in-vmware-identity-manager-catalog-for-vrealize-suite-lifecycle-manager-imported-products\/","title":{"rendered":"How to configure SSO web links in VMware Identity Manager Catalog for vRealize Suite Lifecycle Manager imported products"},"content":{"rendered":"\n
When you deploy a product from vRSLCM its single sign-on link is automatically created in the Identity manager catalog. But if you import an existing vRealize product it will not. Bummer! Or that being said I have not tested importing solutions that already had vIDM configured for authentication without the catalog entry.<\/p>\n\n\n\n
Anyways if you have imported an existing product into vRSLCM and you are missing the SSO link in your catalog. This is how I fixed it (don’t know if this is the official way)<\/p>\n\n\n\n
First you need to enable login with identity manager for the product you want to configure SSO for. When that is done and working do the following for the different products.<\/p>\n\n\n\n