Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORDS 2.0.8/APEX 4.2.5 failing on invalid username password

Maris GabalinsJul 7 2014 — edited Aug 18 2014

Using sample HR application, executing GET fails (http://app.limbo.lv/apex/dev/mflow/hr/employees/) generates debug output - see below.

Obviously MFLOW is correct user, I just do not know how to supply password. Anyone can help with some ideas ?

Interestingly enough at some moments it seems working, however mostly not. Probably depends on which exact session in pool gets reused, if session happens to have corect username it works, if not - fails. Just hypothesis. Anyway WHERE can I specify password for user which to access?

Sincerely

Maris

------------------------------------------------------------------------

Request Path passes syntax validation

Mapping request to database pool: PoolMap [_failed=false, _lastUpdate=1404580651471, _pattern=/dev/, _poolName=ora12-dev, _regex=null, _type=BASE_PATH, _workspaceIdentifier=null, _serviceName=null]

Applied database connection info

Attempting to process with PL/SQL Gateway

Not processed as PL/SQL Gateway request

Attempting to process as a RESTful Service

Determining if request can be dispatched as a Tenanted RESTful Service

Request path has one path segment, continuing processing

No Tenant Principal established yet, continuing processing

APEX_LISTENER pool exists, continuing processing

Matching tenant exists, continuing processing

Dispatching as tenanted request, with base: http://app.limbo.lv/apex/dev/mflow/, target: hr/employees/, tenant: TenantPrincipal [name=MFLOW]

hr/employees/ matches: hr/employees/ score: 0

Choosing: oracle.dbtools.rt.resource.templates.jdbc.JDBCResourceTemplateDispatcher as current candidate with score: Score [handle=JDBCURITemplate [scopeId=null, templateId=16210102858825705|22222423285388094, uriTemplate=hr/employees/], score=0, scope=SecurityConfig [constraint=none, realm=NONE, logonConfig=NONE], originsAllowed=[], corsEnabled=true]

Determining if request can be dispatched as a Tenanted RESTful Service

Request path has one path segment, continuing processing

Tenant Principal already established, cannot dispatch

Chose oracle.dbtools.rt.resource.templates.jdbc.JDBCResourceTemplateDispatcher as the final candidate with score: Score [handle=JDBCURITemplate [scopeId=null, templateId=16210102858825705|22222423285388094, uriTemplate=hr/employees/], score=0, scope=SecurityConfig [constraint=none, realm=NONE, logonConfig=NONE], originsAllowed=[], corsEnabled=true] for: GET hr/employees/

Choosing: oracle.dbtools.rt.jdbc.entity.JDBCTenantDispatcher as current candidate with score: Score [handle=oracle.dbtools.rt.jdbc.entity.TenantDispatcherBase$TenantTarget@209d7383, score=1, scope=SecurityConfig [constraint=none, realm=NONE, logonConfig=NONE], originsAllowed=[], corsEnabled=true]

Chose oracle.dbtools.rt.jdbc.entity.JDBCTenantDispatcher as the final candidate with score: Score [handle=oracle.dbtools.rt.jdbc.entity.TenantDispatcherBase$TenantTarget@209d7383, score=1, scope=SecurityConfig [constraint=none, realm=NONE, logonConfig=NONE], originsAllowed=[], corsEnabled=true] for: GET mflow/hr/employees/

mflow/hr/employees/ is a public resource

hr/employees/ is a public resource

Using generator: oracle.dbtools.rt.json.query.JSONQueryGenerator

Performing JDBC request as: MFLOW

Error during evaluation of resource template: ORA-01017: invalid username/password; logon denied

WebException [statusCode=500, reasons=[Error during evaluation of resource template: GET hr/employees/, SQL Error Code: 1,017, SQL Error Message: ORA-01017: invalid username/password; logon denied
]]

Comments

Maris Gabalins

Hi,

To make it more exciting ...

Starts working correctly after executing "Reset sample data"

Stops working after re-creation of APEX workspace schema.

Sincerely

Maris

patfmnd

Hi, Maris,

Did you get any resolution to this issue?  We started getting this message after a recent clone of our database.  We had cloned our database in past and then restored the schema that was providing our RESTful services with no issues.  Now when we try to call the RESTful services we are getting this error.  Most recently, it happened after a TEST clone from PROD.  DEV was working fine.  We just cloned DEV from PROD and now DEV is also giving this same error message -- as a result our RESTFul service calls end with this error message!

Any suggestions would be appreciated.

Pat

1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 15 2014
Added on Jul 7 2014
2 comments
1,667 views