Secure the password of the schema in the application server

Hi,
my application is using one schema, and the users are stored in a table within that schema. When the user run the application, the schema password is not required since it is stored in formsweb.cfg file as userid=username/password@servicename. the problem with this, is that anyone is able to know the schema password by opening the formsweb.cfg.
is there any way to make the password invisible in the application server ?
Thanx

Hi
1. What is the version of the Oracle Fusion Middleware you are using?
2. Why would the users have access to the formsweb.cfg file?
Please provide the above info to get further assistance.
Regards,
Durbanite

Similar Messages

Maybe you are looking for

  • Not able to see data in the qualifier table of the main tbl , Data Manager

    Hi, I have an issue of not able to see the data of two qualified table after populating them. It is in mdm-5.5 ps4. When populating data first time ,it shows up in those two table slots in the right side of the Data Manager. However subsequently it d

  • Trying to send Calendar invites to "groups"

    Because of issues with our Exchange server, we are forced to use a backup calendar until server is fixed or replaced.  (Calendar events are not showing up, disappearing, etc.)  Attempting to use Calendar (brand G) on our IPhones, but having some prob

  • RE: Subclass windows

    Prasad: Good point!! If Forte went to fully dynamic binding, the problem would likely go away. The core problem appears to be that non-window classes are bound at 'compile' time. Window classes are bound at both initial code creation and compile time

  • Number of entries in the list industry sector varies (Transaction MM01)

    Hell friends I have 2 different ECC servers. When I try to create a material using transaction MM01, I see different lists on them. Both of them were installed recently and so everything available there are standard SAP created data. When I enter tra

  • Migrating to a new Messenger server

    Our current physical mail server, running both GW and Messenger, is a bit long in the tooth. We've migrated away from GW into a unified Exchange-based system, but the GW server is still active for some archival mailboxes that were not migrated for wh