{"id":221,"date":"2014-07-11T09:24:56","date_gmt":"2014-07-11T09:24:56","guid":{"rendered":"http:\/\/faq.graven-ict.nl\/wordpress\/?p=221"},"modified":"2018-02-28T19:40:50","modified_gmt":"2018-02-28T19:40:50","slug":"crontab-user-not-allowed-to-access-to-crontab-because-of-pam-configuration","status":"publish","type":"post","link":"https:\/\/wiki.graven-ict.nl\/wordpress\/crontab-user-not-allowed-to-access-to-crontab-because-of-pam-configuration\/","title":{"rendered":"Crontab: User not allowed to access to (crontab) because of pam configuration"},"content":{"rendered":"<p>Vandaag kreeg ik een melding dat 1 van de (functionele users) gebruikers niet meer de crontab kon editen. op deze systemen loggen de gebruikers in met een ldap user account. en middels een &#8220;sudo su &#8211; username&#8221; switchen ze naar het functionele account.<\/p>\n<pre> [talend@serverA ~]$ crontab -e\r\n Authentication token is no longer valid; new one required\r\n You (talend) are not allowed to access to (crontab) because of pam configuration.\r\n<\/pre>\n<p>De user is gewoon bekend in cron.allow dus is het een andere probleem. waarschijnlijk is het pasword expired<\/p><div id=\"grave-1555963170\" class=\"grave-content grave-entity-placement\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-1970734611769428\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:inline-block;width:728px;height:90px;\" \ndata-ad-client=\"ca-pub-1970734611769428\" \ndata-ad-slot=\"1820224830\"><\/ins> \n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div>\n<pre> [root@serverA]# chage -l talend\r\n Last password change                                   \u00a0: Feb 06, 2014\r\n Password expires                                       \u00a0: Apr 03, 2014\r\n Password inactive                                      \u00a0: never\r\n Account expires                                        \u00a0: never\r\n Minimum number of days between password change         \u00a0: 0\r\n Maximum number of days between password change         \u00a0: 56\r\n Number of days of warning before password expires      \u00a0: 7\r\n<\/pre>\n<p>ja het het password was inderdaad verlopen, je kan de password expire aanpassen met chage<\/p>\n<pre> [root@serverA]# chage -I -1 -m 0 -M 99999 -E -1 talend\r\n<\/pre>\n<p>en weer even ter controle.<\/p>\n<pre> [root@serverA]# chage -l talend\r\n Last password change                                   \u00a0: Feb 06, 2014\r\n Password expires                                       \u00a0: never\r\n Password inactive                                      \u00a0: never\r\n Account expires                                        \u00a0: never\r\n Minimum number of days between password change         \u00a0: 0\r\n Maximum number of days between password change         \u00a0: 99999\r\n Number of days of warning before password expires      \u00a0: 7\r\n<\/pre>\n<p>hier na kan de user gewoon crontab -e gebruiken.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Vandaag kreeg ik een melding dat 1 van de (functionele users) gebruikers niet meer de crontab kon editen. op deze systemen loggen de gebruikers in met een ldap user account. en middels een &#8220;sudo su &#8211; username&#8221; switchen ze naar het functionele account. [talend@serverA ~]$ crontab -e Authentication token is no longer valid; new one ..<\/p>\n<div class=\"clear-fix\"><\/div>\n<p><a href=\"https:\/\/wiki.graven-ict.nl\/wordpress\/crontab-user-not-allowed-to-access-to-crontab-because-of-pam-configuration\/\" title=\"Meer lezen...\">Lees meer<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[16],"tags":[],"class_list":["post-221","post","type-post","status-publish","format-standard","hentry","category-users-en-groepen"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/posts\/221","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/comments?post=221"}],"version-history":[{"count":1,"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/posts\/221\/revisions"}],"predecessor-version":[{"id":222,"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/posts\/221\/revisions\/222"}],"wp:attachment":[{"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/media?parent=221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/categories?post=221"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki.graven-ict.nl\/wordpress\/wp-json\/wp\/v2\/tags?post=221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}