This content has been marked as final. Show 33 replies
That's not entirely accurate. You do not state your OS or Database release. Features vary depending on the database release, and platform and without
these, it's more difficult to trace the problem. I am working with Oracle Database 11g and have no issues. The handling of password expiration was changed in 1.5.4. to fix the issues encountered in earlier releases. The change now means that when a password expires, which is handled by the database, you can reset the password using the Reset Password menu item in SQL Developer. This is only enabled if OCI is available. (You can use the thin driver in your connection). Note that when the password expires and you try to connect, you get an error message, stating that the password has expired.
Beyond that, if there are specifics that you are encountering, please post the details on the forum and we can address them.
I am running 11gR1 client on XP SP3 connecting to 10.2.0.4 database on Solaris 10.
I downloaded Oracle SQL Developer for Windows. (This zip file includes the JDK 1.5.0_06)
It does not work out of the box or DOA.
I have been long waiting for the option as the users have been changing expired using SQL*Plus.
I would be delighted if you show me what I need to do to make it work.
I would be interested in your response to Keith as we are experiencing the same issue here. When a users is set to password expire and we connect with SQL Developer 1.5.4, we get the password expired message. We then select Reset Password and get a 'ORA-01017 invalid username/password; logon denied' message.
The Reset Password dialog box appears not to be sending the Username as a response. I have a bug logged (8462868) for this issue. My OWC session summary is as below:
The problem occurs for SQL Developer connections that do not have username stored. The problem does not occur for those connections that do have the username stored. This is exactly what the Developer in bug 8460869 meant.
Problem is that the username from the reset password dialog is not used. We proved this by successfully resetting a named connection's password (SQL Developer connection that has a username stored) even after we changed the username in the reset password dialog box!
Suppose you have two database users, A and B.
You create a connection 'test' with user A.
You connect using this connection for user A.
Now you disconnect, and the invoke the reset password menu.
Here you change the suggested user from A to B.
You fill in the old password from A (!) and a new password.
The password reset succeeds (!) for user A (!!).
Even if you specified user B in the reset password menu.
When you want to reset user B's password, using connection 'test', you cannot just change the populated 'A' into 'B' in the reset password menu. It looks like you need to be connected to the database first. In other words, connect using 'test', using user 'B'. After that, the last user is somehow remembered by SQL Developer. It is this username that is populated in the reset password menu. And it is this account that will be used in the password reset.
As a consequence, you cannot reset expired passwords this way because you always need a successful connect before the correct username is populated in the reset password menu.
(I was able to reset an expired password using a named connection created for the specific user, before connecting once, however.)
All this makes it impossible for Alan to distribute multiple SQL Developer installations to multiple end users and multiple PCs without having to pre-create all possible named SQL Developer connections ...
Agreed that I update the bug, and that Alan will check the SQL Developer forum to see how others deal with similar scenarios.
Has anyone found the same issue as me with this?
A cascade problem, which I believe also needs attention:
1) SQL Developer said: "pw expired" [no option to change, as noted earlier]
2) I open Toad to change the PW [I know, I know...but I still need Toad for some things like "export" without quotes]
3) After changing it, I return to Developer to reset it in the connection properties
4) Left click on connection (oops)...Developer attempts to connect a few times.
5) Right click to access properties...Developer attempts to connect a few times.
6) Property sheet comes up, but by now the account is locked because developer banged away with the wrong PW too many times.
While our lockout policy may be ultra-conservative I'm sure it's at least "5 failures". Since I didn't click 5 things in the UI (and for those that I did click I'd not have expected a login attempt) I suggest there are spurrious and superfluous login attempts.
This is more than a nusiance because getting the account reset has a several hour response time in my neck of the woods.
Sue Harper, what do you mean by: Does your install have access to the OCI? Even if you're using the thin driver, it needs the OCI for the reset option.
I have the following setup on a windows xp machine:
Oracle Database 11g Release 1 Client (188.8.131.52.0) for Microsoft Windows (32-bit)
Oracle SQL Developer 184.108.40.206, the one with JDK1.6._11 , 129megs
What exactly do I need to do in sql developer to make sure sql developer prompts me for a new password?