Unable to open default browser Dbeaver ubuntu azure MFA - database

I trying to connect to azure database using MFa athentication in Dbeaver client (Ubuntu), but when make the conections this message appear and never opne de browser:
Unable to open default system browser.
No se pudo autenticar el usuario en Active Directory (Authentication=ActiveDirectoryInteractive).
java.lang.RuntimeException: Unable to open default system browser
java.lang.RuntimeException: Unable to open default system browser
Unable to open default system browser
Unable to open default system browser
Tnanks

Related

SP2-0310: unable to open file "apex_epg_config.sql"

Hi I have installed Apex on Oracle 19c pluggable database. I have also successfully run the apex_rest_config command. But when I try to configure pl/sql gateway with the command #apex_epg_config.sql Path_to_apexfolder It gives the following error
SP2-0310: unable to open file "apex_epg_config.sql"

Cannot use chectl auth:login or server:shutdown

I am attempting to restart my local eclipse che server after editing some configuration. I attempted to run chectl server:stop, but got this error:
» Error: E_SHUTDOWN_CHE_SERVER_FAIL - Failed to shutdown Eclipse Che server. Login context is not set. Please login
» first.
So I attempted to login with chectl auth:login, but was again presented with an error:
Using https://che-che.169.254.109.208.nip.io/api server API URL to log in
Error: Command failed with exit code 1: oc status
error: you do not have rights to view project "default" specified in your config or the project doesn't exist
I've looked through the documentation, and couldn't find how to create a "default" project
I used chectl server:deploy --platform=docker-desktop to start my server.
I have tried other methods of deploying che, but it only worked when using Docker desktop without helm.
I am using Windows 10 home, and deploying it using Docker desktop (Engine v19.03.13) and kubernetes version v1.19.3.
Edit: I have filed a bug report on github: https://github.com/eclipse/che/issues/18355

Quarkus connect to SQL Server database with kerberos

When I try to run my Quarkus application with below command, the connection is established and working fine.
mvn clean compile quarkus:dev -Djava.security.krb5.conf=<path-to-my-krb5.conf-file>
When I want to deploy the application and package it with mvn package and then want to run the jar file, the connection to the database cannot be established.
java -jar -Djava.security.krb5.conf=<path-to-my-krb5.conf-file>
Can anyone help me with what I am doing wrong?
Error message
"Unable to execute the validation check for the default DataSource: Cannot login with Kerberos principal <DB_USERNAME>, check your credentials. Kerberos Login failed: Integrated authentication failed. ClientConnectionId:ed078e2e-addc-4582-9a83-68ad13040df1 due to javax.security.auth.login.LoginException (KrbException: Cannot locate default realm)"

Using MSAL in CloudShell

I've validated the MSAL auth path using the desktop PowerShell 5.1 and 7.0 applications. However, all of the authentication paths which worked on the desktop are not working in CloudShell -
PS /home/michael/CSTest/0.0.2/MicrosoftTeams> connect-microsoftteams
Connect-MicrosoftTeams: One or more errors occurred. (Unable to open a web page using xdg-open. See inner exception for details. Possible causes for this error are: xdg-open is not installed or it cannot find a way to open an url - make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com )
Connect-MicrosoftTeams: Unable to open a web page using xdg-open. See inner exception for details. Possible causes for this error are: xdg-open is not installed or it cannot find a way to open an url - make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com
Connect-MicrosoftTeams: No such file or directory
Connect-MicrosoftTeams: One or more errors occurred. (Unable to open a web page using xdg-open. See inner exception for details. Possible causes for this error are: xdg-open is not installed or it cannot find a way to open an url - make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com )
PS /home/michael/CSTest/0.0.2/MicrosoftTeams> connect-microsoftteams -UseDeviceAuthentication
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code BRZPG2UNE to authenticate.
Connect-MicrosoftTeams: One or more errors occurred. (Windows Data Protection API (DPAPI) is not supported on this platform.)
Connect-MicrosoftTeams: Windows Data Protection API (DPAPI) is not supported on this platform.
Connect-MicrosoftTeams: One or more errors occurred. (Windows Data Protection API (DPAPI) is not supported on this platform.)
PS /home/michael/CSTest/0.0.2/MicrosoftTeams> connect-microsoftteams -AccountId miluong#microsoft.com
Connect-MicrosoftTeams: One or more errors occurred. (Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error: )
Connect-MicrosoftTeams: Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error:
Connect-MicrosoftTeams: Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error:
Connect-MicrosoftTeams: One or more errors occurred. (Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error: )
How do I enable support for managed identity?
How do I get interactive auth flow to work without xdg-open? Currently CloudShell does not install xdg-open
Is there a recommended path to try to acquire a token without DPAPI? CloudShell works in a Linux environment and DPAPI only supports Windows.
Do you know of any PS modules which use MSAL that are working in CloudShell?
xdg-open does not work and is not planned to be supported in CloudShell
The DPAPI error was because I was trying to protect the token by encrypting it at rest
Integrated Windows Authentication is not a supported workflow in CloudShell because it's a Linux based environment.

Kinect DK Create Recording

Just received the new Kinect DK and installed the SDK on a W10 machine, then run
C:\temp>k4arecorder.exe -l 5 output.mkv
libusb: error [winusbx_open] could not open device \\.\USB#VID_045E&PID_097C#000041292112#{A5DCBF10-6530-11D2-901F-00C04FB951ED} (interface 0): [5] Access is denied.
[2019-07-03 16:53:10.760] [error] [t=9816] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (305): find_libusb_device(). Unable to open LIBUSB at index 0
[2019-07-03 16:53:10.761] [error] [t=9816] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (68): usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
[2019-07-03 16:53:10.762] [error] [t=9816] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\sdk\k4a.c (129): depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()
Runtime error: k4a_device_open() failed
Runtime error: k4a_device_get_serialnum(device, serial_number_buffer, &serial_number_buffer_size) returned 1
The cmd window was started in Admin mode, as was the viewer. Seems I cannot record on W10, but it works as described in Ubuntu 18.04. Seems it's an access condition, but not sure where.
the reason you cannot open the device is because you connected it to the wrong port. Check out https://learn.microsoft.com/en-us/azure/Kinect-dk/troubleshooting#usb3-host-controller-compatibility and try to connect the device to a different USB port.
We are working to try to make this error clearer. Access denied from libusb could also be due to the handle already being in use by another instance. On Windows you may also have the camera disabled (either you our a company policy). Check Settings -> Privacy for the global camera state.

Resources