Automatically deny access to users after expiry date

Hi All,
Is there any feature in SQL Server that automatically revert back all permissions of a user after certain days(Expiry date).
My company has a policy that all users permissions should be reverted back after every 60 days from request. After 60 days the users should request again for the access.
I am planning to automate this. Any input is appreciated
Thanks,

Hi,
Never don't use the Agent job for security missions.
The Agent may skip a mission for one reason or another (eg problems related to the clock as set the system clock into the future and skip the scheduled time). That may lead to the fact that he is not scheduled to run that mission next. The Agent scheduled
his next mission A executable each time he execute the mission A. Moreover there are several known bug which include stopping the Agent as randomly stops when you schedule the job to run past midnight (There is a fix fro this), etc. The basic idea that
I want to say is NEVER use the Agent schedule for security mission.
http://support.microsoft.com/kb/2598903
as I mention in preview post I think that a trigger on logon is fit for this case (links are on my preview down)
[Personal Site] [Blog] [Facebook]

Similar Messages

Behaviour of "Disable/Delete User After End Date" Task

Hi Expert,
We ran the given OOTB task "Disable/Delete User After End Date" and the behavior is always delete. How,if possible, to change the behavior to disable?
Thanks in advance.
SK

In order to change the behavior, you have to set the system manager preference called "Period to Delay User Delete" to something bigger than the task will make the user disabled and will automatically delete them at a future date.

OIM 11g - User Not enabled After the job "enable user after start date"

Hi,
I have a future hired user in OIM whose start date is set in OIM. The status of the user in OIM is 'Disabled Until Start Date'.
After the start date has passed and the scheduled job 'enable user after start date' is run, I see that the user is still in the status 'Disabled Until Start Date'. I re-run the scheduled job 'enable user after start date', this time manually, still the state of the user remains unchanged.
Please help in troubleshooting as to find out the root cause of the issue and a workaround/solution, if possible.
This issue is intermittent and has happened with quite a number of user. Any pointer would be helpful.
Regards,
Sudipto S.

I agree with Nayan.
One alternative approach can be to write your own custom scheduler which can overcome the limitation of OOTB scheduled job 'enable user after start date'. Let the OOTB job get executed first. After it, your custom scheduler should fire a simple SQL Query:
SELECT USR_KEY, USR_STATUS FROM USR WHERE (USR_START_DATE > SYSDATE -1) AND USR_STATUS='Disabled Until Start Date';
//Means those users who are supposed to get enabled today and are still not yet enabled and are in 'Disabled Until Start Date'. May be 2-3 user keys at max will come...
As you said it happens only intermittently and not for all users... So, let the OOTB scheduled job take care of most of such users... And after it has finished, if any user still remains in 'Disabled Until Start Date', your custom scheduler should enable it via using tcUserOperationsIntf.enableUser(userKey);
Using API is always better than database update... Because APIs trigger downstream provisioning workflows as well and not just updates OIM Database...
Keeping your constraints in mind, I think it is the correct answer.

Reminder mail to users after expiry of their password

Hi All,
Does OAM able to send reminder mail to users after expiry of their password? If yes how?
Regds
Manoj

Sounds like you are looking for something like a thread that watches the age of the password in the directory and notifies the user when an 'expiry' event is detected (based on the clock).
There is nothing in the product that is time or 'monitor' based. You could easily build such a service and execute it from the system (cron / scheduled tasks). Consume obPasswordCreationDate and work your magic from there. I've also had some good success building on such features using quartz [http://www.opensymphony.com/quartz/].
All OAM event process are based on user initiated events - login in the case of password expiry notification warning.
Mark

ALUI Publisher 6.4 - deleting of content items after expiry date

Hi, We have a requirement to delete content items from Publisher after the expiry dates. Is there a process to do this within ALUI Publisher 6.4? Appreciate any suggestions or thoughts. Thanks.

I work with publisher for a long time now, and I don’t think that there is an automatic process that dose that, you have to manually delete it when it is expired.
-Lilach

How can I change the User Password expiry date

Hi,
I want to know how can I change the password expiration date of my user without changing his password. For eg:-
User password expires on 12th May 2007. I want to extend to 12th Jun 2007. Is there any option in Oracle.
Alter User <USERNAME> password expire .....<to new date>;

The command is not alter user set expire...
You should modify the user's profile, and set a timeframe:
ALTER PROFILE DEFAULT LIMIT
PASSWORD_LIFE_TIME = num_of_days;
This way your password will be valid from the last time it was changed and for the time frame previously defined.
~ Madrid.

Why are some websites, such as the FAFSA (federal financial aid for students) website or the BNY Mellon website, denying access to users running Firefox versions newer than 3.6?

Why are some websites that are important to many people, such as the FAFSA (federal financial aid for students) website or the Bank of New York Mellon website, not permitting access to computers running Firefox versions newer than 3.6 when Mozilla is claiming that 5.0 is more stable and secure?
The following information was displayed in regards to this issue -
https://fafsa.ed.gov/FAFSA/app/errors?page=incompatibleBrowser
"An Incompatible Browser Has Been Detected:
Your Web browser is not supported by our Web site. You must use a Compliant Web Browser - Standard* to view our site properly. We recommend you upgrade to the latest version of your browser according to your Operating System.
Supported Mozilla Firefox browsers:
Windows XP - Mozilla Firefox 3.5.x and 3.6.x
Windows Vista - Mozilla Firefox 3.5.x and 3.6.x
Windows 7 - Mozilla Firefox 3.5.x and 3.6.x
Macintosh Operating System 10.5 - Mozilla Firefox 3.5.x and 3.6.x
Macintosh Operating System 10.4 - Mozilla Firefox 3.6
*Compliant Web Browser - Standard
For the past few years, every major Web browser released has been built around a set of open standards designated by the World Wide Web Consortium, a non-profit organization charged with overseeing the continuing development of the Web. What this means is that one piece of code now looks the same on every modern browser, whether it be Internet Explorer, Firefox, Safari, Opera, or others. The majority of our users are using these modern browsers, so we can present content which is optimized for them. "

That is a question for those websites to answer. Firefox 4.0 was released almost 4 months ago, IMO more than enough time for those 2 websites to verify that Firefox 4 & 5 are compliant with W3C standards.
To be able to access that FAFSA website, my advice is to install the Portable Firefox 3.6.19 version to your hard drive. It won't affect your other Firefox installation. <br />
http://portableapps.com/apps/internet/firefox_portable/localization#legacy36

Automatically log in multiple users after reboot

Upon rebooting a shared Mac, is there a way to log in multiple user accounts and run their associated startup items?

No. Each account needs to log in.

GTC Upload in OIM 9.1.0.2.How to capture User Expiry Date

Hi,
There are two OOB fields on User form.User account Expiry Date and User account Expiry Warning date.I have made these fields hidden.I found a strange thing happening.When I create a user manually,these two fields have a date value populated automatically,but if I perform bulk Upload,there two fields are blank.
Please help.
Regards,
Shubhra

Hi srini,
thanks for your reply,
Actually we integrated with 2003 exchange server, and we need a new integration with exchange server 2010.
we don't want to disturb 2003.
We are confusing with connector versions and how to perform those things.
Thnaks,
Valli

Problem in setting user end date from oim to account expiry date in AD process form

Hi all,
i am updating the user end date from oim to user account expiry date in ad process form using oim api.
i am able to get the end date value from oim but when i am setting it using api it through exception but all other attribute i am able to update in process form.
i am facing the problem only with end date field because of different date format in OIM and AD .
so please suggest me what are date format in Active Directory and how can i change the oim date format to Active directory time format in in my java code.

Thanks for the reply.
But all iplanet users need not contain end date attribute, and its an update on existing user.
Can you please ellaborate more on Transformation class..?? example should be helpful.

AD Id Expiry date output

Hello All,
In our organisation, we have temp employee for whom we create a AD Id and set the user account expiry date of 45 days after creation of AD Id.
We have been asked to generate the list of temp employee on weekly basis whose AD Id is going to expiry in current week and need to send email notification, informing their AD id is going to expiry after "x" no.of days.
I was able to create a powershell to find, Can you please confirm if is it correct
Search-ADAccount -AccountExpiring |
Get-ADUser -Properties givenName,sn,userprincipalname,accountExpirationdate.
Thanks HA

Here is the link. If this fails let me know
http://www.microsoftpro.nl/2011/07/07/how-to-schedule-a-powershell-script-using-scheduled-tasks-in-windows-server-2008-r2/
Your code should be like this
Search-ADAccount -AccountExpiring -TimeSpan '7' |
Select -Property givenName,sn,userprincipalname,accountExpirationdate |
Export-Csv -Path C:\Temp\AccountExpiresinSevenDays.csv -NoTypeInformation -Encoding UTF8
Start-Sleep 10
Send-MailMessage -From '' -To '' -SmtpServer 'SMTP' -Subject 'Account Expiry Report' -Attachments C:\Temp\C:\Temp\AccountExpiresinSevenDays.csv
Note: Input From, to SMTP names as required. This is only for your managers reporting needs
Regards Chen V [MCTS SharePoint 2010]

User - Maximum logon duration, set expiry date ?

Hello,
Wanted to know whether BPC NW supports user setting of:
Maximum duration logon; does the session become inactive after a certain amount of time in case you do not execute anything?
Expiry date of user; can you set expiry dates and does a user automatically expire when you donu2019t log on for a certain amount of days?
appreciate inputs.
Thanks.

Hi Ellora,
I don't think if it possible in BPC NW, where as in BPC MS version we have Management Console which gives info. about will all users who have been online for the given period of time.
In BPC NW we have User Activity. BPC logs user and administrator behavior by recording information about each remote function call made from .NET to ABAP.
Regards,
Raghu

Apache user dir (13)Permission denied: access to /~simha/ denied

I am getting Access forbidden! when I am trying to connect to http://localhost/~simha/ where simha is my user name
my /var/log/httpd/error_log says
[Thu Jul 08 17:44:30 2010] [error] [client 127.0.0.1] (13)Permission denied: access to /~simha/ denied
I tried a lot and gave up. Can any one help me in this in regard
The following are the permisions of my home dir simha and public_html
drwx--x--x 130 simha users 16384 Jul 8 17:04 simha
drwxr-xr-x 2 simha users 4096 Jul 8 17:02 public_html
The following are my httpd.conf
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
# with ServerRoot set to "/etc/httpd" will be interpreted by the
# server as "/etc/httpd//var/log/httpd/foo_log".
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "/etc/httpd"
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
Listen 80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule php5_module modules/libphp5.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User http
Group http
</IfModule>
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/srv/http"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "/srv/http">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks includes
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "/var/log/httpd/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
<IfModule log_config_module>
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
CustomLog "/var/log/httpd/access_log" common
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "/var/log/httpd/access_log" combined
</IfModule>
<IfModule alias_module>
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
</IfModule>
<IfModule cgid_module>
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#Scriptsock /var/run/httpd/cgisock
</IfModule>
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
<IfModule mime_module>
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
TypesConfig conf/mime.types
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#AddType application/x-gzip .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
Include conf/extra/httpd-autoindex.conf
# Language settings
Include conf/extra/httpd-languages.conf
# User home directories
Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# phpMyAdmin configuration
Include conf/extra/httpd-phpmyadmin.conf
# Various default settings
Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
Include conf/extra/php5_module.conf
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
The following are my /etc/httpd/conf/extra/httpd-userdir.conf
# Settings for user home directories
# Required module: mod_userdir
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received. Note that you must also set
# the default access control for these directories, as in the example below.
UserDir public_html
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
<Directory /home/*/public_html>
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes SymLinksIfOwnerMatch ExecCGI
<Limit GET POST OPTIONS PROPFIND>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS PROPFIND>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>
I also tried adding user to the group http. BUt nothing is working.

Do you have [or more like lack] +x on the user folder?

Cash Discount if F110 being considered even after expiry of due date

Hello SAP Consultants,
I have setup a payment term for client which is 1% disc if paid within 10 days of invoice date. On running automatic payment program F110, irrespective of no. of days, the payment program generates discount of 1%. (I am using standard payment method C-cheque)
My doubt is why SAP is applying cash discount in F110 even when the payment is being made after 10 days say after a month.
I have cheched the setting in FBZP in All company Codesfor Maximum Cash Discount. The tick is not there means it is not activated. Still we are getting the above error in F110.
Regards,
Abhishek

Hi Abhishek,
The problem you're experiencing is caused by your payment term configuration, which probably has 1% 5 days but does not include how to handle cash discount after that date e.g. 0% 6 days. You can test this quite simply (presuming you have access to a test system) by changing the payment term configuration to include 0% for 6 days then post a vendor invoice with the same details provided in your message and process for payment. Alternatively find an existing vendor invoice with payment term you mention and double click into the vendor line item and add 6 days to the Cash discount days 2 field but leave the Cash discount percentage 2 field blank (see example below) then process for payment. I have also pasted the text from OSS note 48384 below which refers to this issue.
Vendor line item - Additional details tab
Payt terms XXXX Days/percent 5 1.000 % 6 %
Expected results (based on details mentioned in your message):
Payment run posting date: 15/03/10 - Posting date of next payment run: 16/03/10
cash discount still valid and should be deducted
Payment run posting date: 16/03/10 - Posting date of next payment run: 17/03/10
cash discount not valid and should not be deducted
SAP Note 48384 - Cash discount is taken although item overdue
Note Language: English Version: 4 Validity: Valid Since 20.02.1997
Summary
Symptom
Vendor invoice is paid with cash discount by the payment program
although the cash discount period has expired, the "Always max. cash
discount" flag in configuration Payment program is not set and no cash
discount agreement is noted in the document either.
Additional key words
F110, payment run
Cause and prerequisites
If in the terms of payment only, for example, 10 days 3 % and nothing else has been defined (further fields are not filled at all), the payment program has no instructions as to how the payment is to be made if the first cash discount period has expired. Nevertheless, the payment is made with cash discount terms 1 under these circumstances.
Solution
Choose other terms of payment.
Header Data
Release Status: Released for Customer
Released on: 19.02.1997 23:00:00
Master Language: German
Priority: Correction with medium priority
Category: Consulting
Primary Component FI-AP Accounts Payable
The Note is release-independent

Beginner User: Locking (making read only after data entry) a single field after selecting date

Hello, I am a beginner user trying to create a form using Adobe Livecycle. One of the fields I would like to make read only/protect it/password protect it after a user selects the date. For example, I select August 17, 2010 as the date. After I select it, I would like that field to be read only or protected so that another user can not edit it.
I am a complete novice using XML or codes. I'm learning alot from these boards though. I know its probably simple.
Any help is appreciated.

The attached locks a text field if the date chosen is "08-17-2010". If it is not the text field is accessible.
// form1.page1.date::exit - (JavaScript, client)
if (this.rawValue == "2010-08-17") {
form1.page1.tf.access = "protected";
else {
form1.page1.tf.access = "";
Steve

Automatically deny access to users after expiry date

Similar Messages

Maybe you are looking for