Quantcast
Channel: All Centrify Express posts
Viewing all 1833 articles
Browse latest View live

Re: Can we authenticate JupyterHub Ipython notebook server via centrify active directory?

$
0
0

,

 

Welcome to the Centrify Express community,

 

Although the platform is not in the supported list, it sounds (from what I briefly read) that it uses PAM (Pluggable Authentication Modules).

 

Reference: https://jupyterhub.readthedocs.io/en/latest/

Different authenticators control access to JupyterHub. The default one (pam) 
uses the user accounts on the server where JupyterHub is running. If you use
this, you will need to create a user account on the system for each user on
your team. Using other authenticators, you can allow users to sign in with
e.g. a Github account, or with any single-sign-on system your organisation
has.

This means that if the Linux server you're using to front-end is supported by Centrify and it's loaded, it should just work because we provide a PAM module and it's configured automatically.

 

As per the link below, there may be other options.

http://jupyterhub.readthedocs.io/en/latest/api/auth.html

 

 

R.P


Re: SSO with xrdp

$
0
0



 

Welcome to the Centrify Express community.

 

If you're referring to this link:

post.PNG

Unfortunately this is a non-Centrify link.

 

You should be able to lay-out your PAM modules accordingly.  Remember that perhaps the session PAM module does not apply here.

 

Please provide more info, this way we can try to recreate in the lab.

 

a) Version of Centrify

b) Version of Ubunty (target)

c) OS/Version of source.

 

They all should have Centrify and be joined to AD for this setup to work.

 

R.P

Re: Wrong key format

$
0
0

,

 

Welcome to the Centrify Express forums.

 

By default, modern versions of Ubuntu with OpenSSH 7.x won't allow older clients (like the PuTTY client included with 5.3.1) to do the key exchange.

 

From:  http://www.openssh.com/txt/release-7.0

We plan on retiring more legacy cryptography in the next release
including:

 * Refusing all RSA keys smaller than 1024 bits (the current minimum
   is 768 bits)

 * Several ciphers will be disabled by default: blowfish-cbc,
   cast128-cbc, all arcfour variants and the rijndael-cbc aliases
   for AES.

 * MD5-based HMAC algorithms will be disabled by default.

The current supported version of Centrify Express is 5.3.1.  Please upgrade your DirectManage components and repeat your testing.

 

Please

Active Directory Manager Attribute in Samanage

$
0
0

We have configured Centrify to authenticate our Samanage solution however the manager field from Active Directory is not populated in Samanage. The field is populated in the Centrify Cloud config.

Re: Active Directory Manager Attribute in Samanage

$
0
0

Within your provisioning script editor, replace your current script with the script below. This will bring all available attributes from active directory profile into Samanage. 

 

Cloud Manager -> Apps -> Samanage -> Provisioning -> Provisioning Script -> Provisioning Script Editor

 

//#!

 

destination.email = source.Email;

destination.name = source.DisplayName;

 

if (source.OfficePhone != null) {

    destination.phone = source.OfficePhone;

}

else if (source.MobilePhone != null) {

    destination.phone = source.MobilePhone;

}

else if (source.HomePhone != null) {

    destination.phone = source.HomePhone;

}

 

destination.title = source.Get('title');

 

site.name = source.Get('physicalDeliveryOfficeName');

if (site.name)

{

    destination.site = site;

}

 

department.name = source.Get('department');

if (department.name)

{

    destination.department = department;

}

 

reports_to.email = source.Get('ReportsToEmail');

if (reports_to.email)

{

    destination.reports_to = reports_to;

}

Re: Wrong key format

$
0
0

Hi Robertson,

 

Thanks for the reply and the welcome! 

 

As far as versions are concerned, I'm running version DirectManage 5.3.1.368 so that should be supported. That includes PuTTY version 0.64 (0.67 seems to be the latest stable direct from PuTTY) in the installation. 

 

As far as Ubuntu is concerned, that's 12.04.5 LTS, running OpenSSH 1:5.9p1-5ubuntu1.10 from the default ubuntu repositories. 

 

Essentially, everything should be supported as far as I know.

 

This feels like a syntax issue... DirectManager is expecting the private key in a particular format. What's particularly strange about it is that as far as I can tell, it's calling the putty.exe in the External folder with some cli arguments. When I run that same command manually from command prompt with the same exe, it works. 

 

Any thoughts?

 

Cheers,
Sam

 

Re: Wrong key format

$
0
0

Did you convert the key to the PuTTY format using PuTTYGen?

Re: Wrong key format

$
0
0

The key was generated in PuTTYGen perhaps two weeks ago. It's an SSH2-RSA 2048 bit. 

 

Additionally, I've attemtped this with a Ubuntu 16.04 server as well, same results as my first post.


Centrify Browser Extension has fired an exception - Internet Explorer

$
0
0

The browser extension in Internet Explorer 11 is displaying the following error message:  'Centrify Browser Extension' has fired an exception.  Click the 'Details" button to see the detailed informatino about the error.

Integrate Google and Facebook Social Login

$
0
0

Hello,

 

I am new to Centrify and I started learning it. Well, I tried to integrate the Google and Facebook login in the registration with social logins. I understand that we have to do certain config setup in google and facebook side especially "Valid OAUTH Redirect URI" is the important field. In the centrify document it is said that we have to provide "https://<pod_abcd>.centrify.com" but lets say I am using my trail version (https://aam0561.my.centrify.com) tenant so i tried to provide "https://aam0561.my.centrify.com" for redirect URI in both google and facebook developer account. But no luck, it is returning wrong redirect URI.Do we need to provide App Domains field value in facebook developer account for working ?

 

Please help me out. Appreciate your help. Cheers !

 

Siva,

 

Re: Integrate Google and Facebook Social Login

$
0
0

Hello Siva, 

 

The setup may be easier than it seems. It sounds like your trying to leverage social identities for user logins to Centrify? If so, simply click on the following configuration to enable the specific social identities you would like to leverage. 

 

Screen Shot 2016-08-23 at 1.35.35 PM.png

 

This will allow users to log into Centrify using their social identity with the example below. 

 

Screen Shot 2016-08-23 at 1.38.49 PM.png 

 

 

Re: Integrate Google and Facebook Social Login

$
0
0

Hello Chow,

 

Thanks for the reply. I have already configured those things (Client ID+Secret Key) in Centrify but my question is regarding what should be provided for OAUTH Redirect URI value which supposed to be given at the google or facebook developer account. Please check the below URL centrify document for configuring the Social login.
https://docs.centrify.com/en/centrify/adminref/index.html?version=116#page/cloudhelp%2Fcloud-admin-config-apple.html%23ww1124649. Please let me know if you get any idea. Appreciate it. Cheers !

 

Siva,

Re: Integrate Google and Facebook Social Login

$
0
0

I Would like to get a Email when somebody reverts to me. So enabling checkbox. Thanks !

Re: Integrate Google and Facebook Social Login

$
0
0

The URI (uniform resource locator) is something you will get from the social media provider. Below is an example of how the URI is defined and configured for Facebook as an example - https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow. The purpose of this configuration is to trust one or more web-sites that you want users to be re-directed upon login/logout using social media applications like Facebook. Check with each of your social media providers for the URI that you can enter on the Centrify side for the redirect.

 

Hope this helps.

Support for centos 6.8?

$
0
0

Is there an eta on support for centos 6.8 (for centrify express)?

 

I'm considering moving to centrify, but the directmanage deployment manager chokes on centos 6.8 boxes because it says it doesn't have an available analysis tools package for 6.8.


Re: Support for centos 6.8?

$
0
0

,

 

Welcome to the Centrify Express community:

 

Deployment manager is not neededfor agent functionality, it's just a discovery & distribution mechanism.  You can get the RPM and use rpm, yum, chef, puppet, ansible, whatever you require to install the software.

 

What you're likely seeing is that some of our utilities like will throw an error because CentOS 6.8 is not on the manifest.   Since this is a minor release, you should be able to install the client directly and join AD via any other means.

 

See below.  This is not an "officially-supported" release until Suite 2017, but you can install our client and use it unless there's been major OS-changes for PAM, NSS or Kerberos.

 

Notice below that I used the Centrify repo to obtain the bits, then I ran adjoin and off we go...

 

 

[centrifying@centos68 ~]$ cat /etc/centos-release
CentOS release 6.8 (Final)
[centrifying@centos68 ~]$ sudo yum install CentrifyDC
Loaded plugins: fastestmirror, refresh-packagekit, security
Setting up Install Process
base                                                     | 3.7 kB     00:00
base/primary_db                                          | 4.7 MB     00:01
centrify                                                 | 2.9 kB     00:00
centrify/primary_db                                      |  20 kB     00:00
extras                                                   | 3.4 kB     00:00
extras/primary_db                                        |  37 kB     00:00
updates                                                  | 3.4 kB     00:00
updates/primary_db                                       | 2.0 MB     00:00
Resolving Dependencies
--> Running transaction check
---> Package CentrifyDC.x86_64 0:5.3.1-398 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package             Arch            Version            Repository         Size
================================================================================
Installing:
 CentrifyDC          x86_64          5.3.1-398          centrify           33 M

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 33 M
Installed size: 80 M
Is this ok [y/N]: y
Downloading Packages:
centrifydc-5.3.1-rhel4-x86_64.rpm                        |  33 MB     00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : CentrifyDC-5.3.1-398.x86_64                                  1/1
  Verifying  : CentrifyDC-5.3.1-398.x86_64                                  1/1

Installed:
  CentrifyDC.x86_64 0:5.3.1-398

Complete!
[centrifying@centos68 ~]$  sudo adjoin -w -u dwirth centrify.vms
[sudo] password for centrifying:
dwirth@CENTRIFY.VMS's password:
Using domain controller: dc.centrify.vms writable=true
Join to domain:centrify.vms, zone:Auto Zone successful

Centrify DirectControl started.
Loading domains and trusts information

Initializing cache
.
You have successfully joined the Active Directory domain: centrify.vms
in the Centrify DirectControl zone: Auto Zone


You may need to restart other services that rely upon PAM and NSS or simply
reboot the computer for proper operation.  Failure to do so may result in
login problems for AD users.


[centrifying@centos68 ~]$ adinfo
Local host name:   centos68
Joined to domain:  centrify.vms
Joined as:         centos68.centrify.vms
Pre-win2K name:    centos68
Current DC:        dc.centrify.vms
Preferred site:    Demo-Network
Zone:              Auto Zone
CentrifyDC mode:   connected
Licensed Features: Enabled

 

 

"Officially Supported" to us means that we have QA-tested all our tool-set, but that will happen for that version of CentOs  (released in May, the same month we relased 2016.1) when we release 2017.

 

Bottomline - no need to wait, enjoy automation.

 

R.P

Re: Centrify Browser Extension has fired an exception - Internet Explorer

$
0
0

,

 

Are you an Express or Commercial customer?

You should have the ability to contact support if you're a commercial customer.

 

Otherwise, you should give us more information about this exception.

  • Operating System
  • Application you want to access
  • Exception screenshot

R.P

zone failed

$
0
0
Moved to the Server Suite forum for better topic alignment.

PKI certificates are not being recognized

$
0
0

I am having issues with my certificates being recognized

 

Re: PKI certificates are not being recognized

$
0
0

Hello  and welcome to the Centrify Community. 

 

Regarding PKI certificates, can you explain a bit more about the issue you are having? Are you meaning to post in the Centrify Express for Mac, or Unix?

 

Have a great day!

 

Ryan V.

Viewing all 1833 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>