If you would search as I showed above there was some scenarios where this type of stuff was done, Namely changing md5 to bcrypt. I don't have those links.
Like John has a login in the old system with a password, you match that in the new system with username being the same (but unique) but has to use bcrypt password.
It's just a matter of a match and chain from getting that data from the other user table and matching it up with laravel user table.
Sorry it's just hard to explain this stuff in a post but I think you just think it through you're just doing the actual login in laravel via code, the user isn't actually logging in twice.
But the part about fixing the the bcrypt is a separate process.
Like have a checkbox (or some field) in the user table, and once fixed and bcrypt is set up that can be checked off so it is not repeated.
But yes so hard to explain this in a post.
And of course you will need quite a bit of custom code to make this work.
It would be hard to do a video on this stuff since each situation is unique.
Seems like also you could just use a laravel user a table, and once logged in redirect to Oracle tables as needed.
Obviously there's more than one way to do this.
But however you decide, use at least bcrypt, md5 is not good.