Bug 1809185 - Can't create an instance using WebUI
Summary: Can't create an instance using WebUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DS11.1
: dirsrv-11.1
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-02 14:44 UTC by Viktor Ashirov
Modified: 2020-04-29 08:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-29 08:04:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1961 0 None None None 2020-04-29 08:04:48 UTC

Description Viktor Ashirov 2020-03-02 14:44:59 UTC
Description of problem:
When I fill out the form for instance creation and press Create Instance button, nothing happens.

In the browser console I see:

index.js:15 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://10.0.138.102:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.


Version-Release number of selected component (if applicable):
389-ds-base-1.4.2.8-2.module+el8dsrv+5809+6657a82a.x86_64
cockpit-389-ds-1.4.2.8-2.module+el8dsrv+5809+6657a82a.noarch

Comment 4 Viktor Ashirov 2020-04-20 12:47:55 UTC
Build tested: cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch

I can successfully create an instance. 
The error message mentioned in comment #0 is not related to the bug, it's a different issue.

Marking as VERIFIED.

Comment 6 errata-xmlrpc 2020-04-29 08:04:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1961


Note You need to log in before you can comment on or make changes to this bug.