Yeah, Ryan, you’‘ll see from my first step that I created a new provider rather than editing the default one. Nonetheless, it seems that this provider is being used for gaining access to tables I didn’‘t think it should – and that’‘s what’'s confusing to me.
Are there any other classes that depend on the AuthProvider and UserProvider for access to their database and tables? If so, these are all going to look to my custom database, or at least that’‘s the behavior I’'m seeing.
Thinking about this a bit over the past hour, let me throw out an idea: in my custom classes (MyAuthProvider and MyUserProvider), I use DbConnectionManager.setConnectionProvider to change to my new custom provider for the auth calls. Does this set the provider globally, and thus interfere with any other classes that might be simultaneously (or just after) trying to connect using the DbConnectionManager? On the notion that this might be happening, I even created a new private instance of the DbConnectionManager in each of my custom classes, but this didn’'t help anything.
I’'d be happy to provide links to my custom files, if anyone thinks that this would help decode what might be happening!