Make PAM auth TTL customisable about python-irodsclient

[d-w-moore]

I am not at all sure why the above code sends an AUTH_TTL_KEY value. _login_pam is the function executed at the time of login, rather than the setting of such parameters as time-to-live as is done by iinit. In fact, the python-irodsclient does not innately contain any code that is the equivalent of iinit's function.
On a little different subject - since @sellth mentions iRODS 4.3.1 in the issue description - I'd like acknowledge another ongoing issue: the need to teach the client to go through the new (4.3.0+) auth-framework's pam_password implementation rather than going through the legacy auth.

[sellth]

I am not at all sure why the above code sends an AUTH_TTL_KEY value. _login_pam is the function executed at the time of login, rather than the setting of such parameters as time-to-live as is done by iinit. In fact, the python-irodsclient does not innately contain any code that is the equivalent of iinit's function.

It should define the TTL of pam_pw_negotiated which when saved "obfuscated" in the right place does provide iinit functionality.

python-irodsclient/irods/session.py

Lines 316 to 323 in 96d2cd2

	@property
	def pam_pw_negotiated(self):
	self.pool.account.store_pw = []
	conn = self.pool.get_connection()
	pw = getattr(self.pool.account,'store_pw',[])
	delattr( self.pool.account, 'store_pw')
	conn.release()
	return pw

[d-w-moore]

Ah, ok. I see it now. Thanks @sellth !

[alanking]

@d-w-moore - Please close if complete.