OUD 11g: ODSM Unable To Display User Photo When attempt To Open The Jpg image In a Separate Tab In The Browser
(Doc ID 2219485.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Unified Directory - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
ODSM can't display uploaded jpegPhoto attribute (user profile photo) When attempt to open the jpg image in a separate tab in the browser, the browser returns Error 401 (Unauthorized)
This appears to be an ODSM bug related to permissions in the WebLogic config..
If you populate the jpegPhoto attribute with an encoded jpeg image, ODSM
rightly places a copy of the decoded file in a tempfiles/images directory:
$ ls -1
When you attempt to open the jpg image in a separate tab in the browser, the
browser returns Error 401 (Unauthorized):
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.2 401 Unauthorized
The request requires user authentication. The response MUST include a
WWW-Authenticate header field (section 14.46) containing a challenge
applicable to the requested resource. The client MAY repeat the request with
a suitable Authorization header field (section 14.8). If the request already
included Authorization credentials, then the 401 response indicates that
authorization has been refused for those credentials. If the 401 response
contains the same challenge as the prior response, and the user agent has
already attempted authentication at least once, then the user SHOULD be
presented the entity that was given in the response, since that entity MAY
include relevant diagnostic information. HTTP access authentication is
explained in section 11.
This means that ODSM is not properly granting un-authenticated access to the
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document