![](\"http:\/\/jeffhobbs.com\/wp-content\/uploads\/2007\/10\/mge-login.gif\")
<\/p>\nFor those have connected to an MGE connection using an Oracle database, you’ll recognize this screenshot:<\/p>\n
<\/p>\n
This comes up whenever you open\/close a connection or open a geoworkspace. Personally, even though the MGE connection to an Oracle database is read-only, I think this is a valuable option. On a side note, on some machines you can save the user name and password into the ODBC DNS setup and this will eliminate the need for entering a password at this dialog. This can be done my just embedding the password with the user name like this:<\/p>\n
user\/password<\/p>\n
Anyhow, I’ve always been surprised that Intergraph doesn’t force something similar for an Oracle Object Model connection…ESPECIALLY since this connection can be read\/write! For those that don’t use Oracle with GeoMedia, by default GeoMedia will save the password (hidden) in the .gws. As a result, whenever you load the .gws, GeoMedia will connect to the Oracle database with the user name and password saved in the .gws. Yes, this is convenient. However, it’s not ideal from a security standpoint. Especially if you actually use unique logins in Oracle where User A may only have read\/write to TABLE A while User B may have read-only to TABLE A. To be honest, even from a non-security standpoint, it’s still a bad idea. It’s fairly easy to make a mistake when you’re not paying attention or not expecting to be able to do something to the data. <\/p>\n
So, there is a workaround to force a similar type of login restriction. This can be found in the "Working with GeoMedia Professional" PDF in Appendix B, page B-2. However I’ll post it here as well:<\/p>\n
![](\"http:\/\/jeffhobbs.com\/wp-content\/uploads\/2007\/10\/force-login.gif\")
<\/p>\n