Activity

From 10/04/2023 to 11/02/2023

11/02/2023

12:17 PM Feature #4854: origin affinity: Code review 4854a revision 14804.
The exception caught in @EnvironmentOps.setKeyValue@ should be logged. While th... Hynek Cihlar
10:10 AM Feature #4854: origin affinity: Hmm. The encryption point is a good one. We don't know how this will be used. Even for configuration data, this is... Greg Shah
09:28 AM Feature #4854: origin affinity: If they use the storage / registry for configurations, it won't matter much, otherwise the customers need to use thei... Galya B
09:26 AM Feature #4854: origin affinity: Hynek Cihlar wrote:
> * In @ClientStorageImpl.java@ the copyright message is broken, the line with GNU location is r... Galya B
08:14 AM Feature #4854: origin affinity: Code review 4854a 14792..14803.
The changes look good. Just a couple of points below.
* In @ClientStorageImpl.j... Hynek Cihlar
06:13 AM Feature #4854: origin affinity: Fix in r14803.
Testing methods:
Prerequisite for @localStorage@ as client storage is adding:... Galya B
04:23 AM Feature #4854: origin affinity: I'll go over the major changes in the order they appear with diff:
* With 3931a the login page @web_landing.html@ ha... Galya B
11:32 AM Feature #7997: Encryption for client storage data / registry: Yes, and we need to decide if we would use a server-wide key or if we would implement per-account level keys. Greg Shah
10:27 AM Feature #7997: Encryption for client storage data / registry: What encryption? It should be reversible. Galya B
10:26 AM Feature #7997: Encryption for client storage data / registry: Registry is accessed in 4GL via @GET-KEY-VALUE@ and @PUT-KEY-VALUE@ methods. In FWD registry is backed up by differen... Galya B
10:18 AM Feature #7997 (New): Encryption for client storage data / registry: Galya B

11/01/2023

04:48 PM Feature #4854: origin affinity: Greg Shah wrote:
> Eugenie/Hynek/Sergey: Please review 4854a.
I have no objections in general(just because it is ... Eugenie Lyzenko
02:48 PM Feature #4854: origin affinity: Eugenie/Hynek/Sergey: Please review 4854a. Greg Shah
11:28 AM Feature #4854 (Review): origin affinity: 4854a r14802 ready for review. Based on trunk r14792. Changes solve #4854, #4517 and a few unrelated small issues, in... Galya B
08:26 AM Feature #4854: origin affinity: I'm fine with that so long as it all matches the 4GL behavior. Greg Shah
08:05 AM Feature #4854: origin affinity: Greg Shah wrote:
> Does @GET-KEY-VALUE@ support @NO-ERROR@ in the 4GL?
No, it seems. I don't know what kind of er... Galya B
07:55 AM Feature #4854: origin affinity: Does @GET-KEY-VALUE@ support @NO-ERROR@ in the 4GL? Greg Shah
04:59 AM Feature #4854: origin affinity: How to suppress error from @GET-KEY-VALUE@? The following line produces @expecting DOT, found 'NO-ERROR'@:... Galya B
11:27 AM Feature #4517 (Review): optionally back the 4GL features for Registry access with the user-specif...: 4854a r14802 ready for review. Based on trunk r14792. Changes solve #4854, #4517 and a few unrelated small issues, in... Galya B
07:46 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: It is for consistency of the protocol and for performance. Greg Shah
03:21 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Why is WebSocket messaging using only byte arrays and no text messages? Is there a reason behind that decision or it ... Galya B

10/31/2023

04:35 AM Feature #3931: single sign-on for virtual desktop mode: Guido Brandsen wrote:
> Galya, today we saw a minor problem with client spawning.
> The error shown in OS login was... Galya B
04:30 AM Feature #3931: single sign-on for virtual desktop mode: Galya, today we saw a minor problem with client spawning.
The error shown in OS login was:... Guido Brandsen

10/30/2023

03:34 PM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: I'd prefer if both act the same way (default to preferences). Greg Shah
11:28 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: @Browse@ configs will continue to be saved only in @localStorage@, while registry will fallback to @Preferences@ by d... Galya B

10/27/2023

03:31 PM Feature #4854: origin affinity: Hynek Cihlar wrote:
> With @waitForResult@ you will make @MSG_SET_KEY_VALUE@ effectively synchronous. So I suppose t... Hynek Cihlar
03:28 PM Feature #4854: origin affinity: AFAIK every message deals with errors on its own, we don't have a common error handling mechanism. Look at @GuiWebSoc... Hynek Cihlar
03:24 PM Feature #4854: origin affinity: Galya B wrote:
> Is there any practice already in place for sending back errors from the front-end for WebSocket mes... Sergey Ivanovskiy
03:12 PM Feature #4854: origin affinity: Galya B wrote:
> 5 mil chars is quite a lot for config storage. This @localStorage@ will be available to customers t... Sergey Ivanovskiy
10:23 AM Feature #4854: origin affinity: Is there any practice already in place for sending back errors from the front-end for WebSocket messages? ... if some... Galya B
10:10 AM Feature #4854: origin affinity: > Currently @localStorage@ is used only for the enhanced @browse@ configs. There is no error handling in place. This ... Greg Shah
10:06 AM Feature #4854: origin affinity: Greg Shah wrote:
> I'm OK with storage limitations, so long as we have a consistent behavior that is exposed to the ... Galya B
08:15 AM Feature #4854: origin affinity: I'm OK with storage limitations, so long as we have a consistent behavior that is exposed to the 4GL code as a legacy... Greg Shah
01:48 AM Feature #4854: origin affinity: 5 mil chars is quite a lot for config storage. This @localStorage@ will be available to customers through the registr... Galya B
10:27 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: > It's doable, but then can we make localStorage the non-default, because it's more different?
Yes, that makes sense. Greg Shah
10:15 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Greg Shah wrote:
> Review of #4517-13:
> > Do we want the web under linux to also store in @Preferences.userRoot@? ... Galya B
10:08 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Review of #4517-13:
* Shouldn't the "Shared between" column for the @Win/other@ scenarios that use @LOAD BASE-KEY ... Greg Shah
09:54 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: I'm almost ready with the implementation. Can I have a review of the table? Galya B
09:17 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Greg Shah wrote:
> The table in #4517-13 is about FWD behavior (I think). Is this meant to document the current beh... Galya B
09:16 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Do we want the web under linux to also store in @Preferences.userRoot@? It will be more consistent to everything else... Galya B
09:16 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: The table in #4517-13 is about FWD behavior (I think). Is this meant to document the current behavior before any cha... Greg Shah
09:13 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: > Do we want all web clients always to store registry in the browser for consistency?
No, some customers will want... Greg Shah
09:11 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: The client process for web is on the server if no brokers are configured. And brokers are reused by multiple clients. Galya B
09:11 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Do we want all web clients always to store registry in the browser for consistency? Galya B

10/26/2023

12:05 PM Feature #4854: origin affinity: I guess that solution can be using a local storage for a different origin that extends the common origin. Sergey Ivanovskiy
11:04 AM Feature #4854: origin affinity: It seems that there is an open question how to extent a storage for a user as there is the web storage limit for the ... Sergey Ivanovskiy
10:06 AM Feature #4854: origin affinity: OK. I checked this test for the Firefox, so it follows that the @locationStorage@ storage is used per origin but not ... Sergey Ivanovskiy
09:54 AM Feature #4854: origin affinity: Unfortunately Redmine struggles with the 5MB texts for each value, so if you're not able to copy it from here, copy i... Galya B
09:44 AM Feature #4854: origin affinity: OK, here is the test (inspired by https://arty.name/localstorage.html):
Key 'test' is successfully saved, 'test2' ... Galya B
09:33 AM Feature #4854: origin affinity: I need to prove the Mozilla documentation? It's written in the link you shared https://developer.mozilla.org/en-US/do... Galya B
09:29 AM Feature #4854: origin affinity: I would agree if you proved it by the similar test that the storage is used per origin but not per a key. This test i... Sergey Ivanovskiy
09:11 AM Feature #4854: origin affinity: So do we agree on the change? Galya B
09:03 AM Feature #4854: origin affinity: Nice, I was about to write something. 5200000 chars max in my case. According to https://developer.mozilla.org/en-US/... Galya B
09:00 AM Feature #4854: origin affinity: You can use this test program https://arty.name/localstorage.html that checks... Sergey Ivanovskiy
08:21 AM Feature #4854: origin affinity: Galya B wrote:
> Sergey Ivanovskiy wrote:
> > Why @UserKeyValueStorage@ was removed? What is its substitution? @Use... Sergey Ivanovskiy
04:24 AM Feature #4854: origin affinity: Sergey Ivanovskiy wrote:
> Why @UserKeyValueStorage@ was removed? What is its substitution? @UserKeyValueStorage@ wa... Galya B
03:42 AM Feature #4854: origin affinity: Why @UserKeyValueStorage@ was removed? What is its substitution? @UserKeyValueStorage@ was needed to store large data... Sergey Ivanovskiy
04:43 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: The most obvious problem I see right away is with web users on Windows. All of them would share this "device id" the ... Galya B
03:19 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Storage for @GET-KEY-VALUE@ and @PUT-KEY-VALUE@:
|OS|@LOAD BASE-KEY "INI"@|Client Type|Storage|Storage lifespan|Sh... Galya B

10/25/2023

08:13 AM Feature #4854: origin affinity: Stanislav is the expert in enhanced browse. Greg Shah
08:13 AM Feature #4854: origin affinity: Hotel GUI embedded mode has the enhanced browse activated, but virtual desktop mode doesn't (if I recall correctly). Greg Shah
08:06 AM Feature #4854: origin affinity: For the old @testcases@ project I have these settings ... Sergey Ivanovskiy
07:54 AM Feature #4854: origin affinity: Galya, see this wiki: [[p2j:Browse_Widget_Enhancements]]. Hotel GUI has the enhanced browse (if it doesn't, then thi... Constantin Asofiei
07:51 AM Feature #4854: origin affinity: Sergey, can you help me with an example in 4GL for enhanced @browse@. I don't seem to understand how to enable the ge... Galya B
07:50 AM Feature #4854 (WIP): origin affinity: Although 4854 is done, 4854a will also have the changes for #4517, because both tasks are related in the code. Movin... Galya B

10/24/2023

12:33 AM Feature #3931: single sign-on for virtual desktop mode: Eugenie Lyzenko wrote:
> Galya,
>
> Should the following entries also be removed from @directory.xml@?
>
> [..... Galya B

10/23/2023

03:36 PM Feature #3931: single sign-on for virtual desktop mode: Galya,
Should the following entries also be removed from @directory.xml@?... Eugenie Lyzenko
11:56 AM Feature #3931: single sign-on for virtual desktop mode: 3931a was merged to trunk as rev. 14783 and archived. Galya B
11:34 AM Feature #3931 (Test): single sign-on for virtual desktop mode: Galya B
01:10 PM Bug #7946 (WIP): Default selection and current browse row color differs for different customers a...: Created task branch 7946a from FWD trunk revision 14786. Stanislav Lomany
12:38 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: Very nice work in figuring this out! Greg Shah
12:38 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: Stanislav Lomany wrote:
> Should we add @oldBrowseSelectionBar@ parameter to the directory? E.g. in @server/default/... Greg Shah
11:57 AM Feature #4129: map web client users to OS accounts: 3931a was merged to trunk as rev. 14783 and archived. Galya B
11:34 AM Feature #4129 (Test): map web client users to OS accounts: Galya B

10/22/2023

07:17 AM Feature #4856 (WIP): web client session forking: Galya B

10/21/2023

10:41 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: Should we add @oldBrowseSelectionBar@ parameter to the directory? E.g. in @server/default/theme/oldBrowseSelectionBar... Stanislav Lomany
10:29 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: I found the cause of the issue. This picture from my earlier investigations which illustrates the difference between ... Stanislav Lomany

10/20/2023

08:26 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: > @app_A@ - Windows Server 2012 + OE 11.x
> @app_C@ - Windows Server 2016 + OE 10.x (!)
> @app_M@ - Windows Serve... Greg Shah
04:37 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: While @app_C@ and @app_M@ have different row color, the @HKEY_CURRENT_USER\Control Panel\Colors@ sections are the sam... Stanislav Lomany
04:33 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: We have differences in "selection color" which affects color of selection in fill-in, editor, drop-downs and selectio... Stanislav Lomany
02:27 AM Bug #7946 (Test): Default selection and current browse row color differs for different customers ...: Stanislav Lomany

10/19/2023

12:51 AM Feature #4856: web client session forking: The core requirement of the task is to open a new session of the same user easily without dialogs. That is achieved w... Galya B
12:39 AM Feature #4129: map web client users to OS accounts: You're referring to a very old comment, where I'm trying to figure out the point of the trusted security check that w... Galya B
12:37 AM Feature #4129: map web client users to OS accounts: Greg Shah wrote:
> I'm worried that the code is now written to force the storage of the password when customers will... Galya B
12:33 AM Feature #4854: origin affinity: Constantin Asofiei wrote:
> Some notes about the diff:
> * the testing I think can be done with Hotel GUI and enhan... Galya B

10/18/2023

04:42 PM Feature #4129: map web client users to OS accounts: > > > All OS users will have to have password defined for web, because the spawner does PAM authentication for the we... Greg Shah
02:24 PM Feature #4854: origin affinity: Some notes about the diff:
* the testing I think can be done with Hotel GUI and enhanced browse - this uses this sto... Constantin Asofiei
09:00 AM Feature #4856: web client session forking: > I'm pretty sure it's not expected the 4GL app to be subscribed for an event from web for a new forked session.
I... Greg Shah
08:59 AM Feature #4856: web client session forking: > You can have different users logged in with auto-login.
Please help me understand how this can work. Auto-login... Greg Shah
08:46 AM Feature #4856: web client session forking: I'm pretty sure it's not expected the 4GL app to be subscribed for an event from web for a new forked session.
Galya B
08:43 AM Feature #4856: web client session forking: You can have different users logged in with auto-login. This is not related to opening a new session (so called `fork... Galya B
08:33 AM Feature #4856: web client session forking: Our discussion in #7813 highlights that I did not pick up on a crucial detail.
> Also it dawned on me just now tha... Greg Shah

10/17/2023

04:41 AM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: Tomasz Domin wrote:
> There are two issues:
> first - there is no label on initial screen, the issue is caused by a... Tomasz Domin

10/16/2023

11:22 AM Feature #4854: origin affinity: Sergey Ivanovskiy wrote:
> Ok. In this case you should create a branch or use the existing branch. I guess your chan... Galya B
09:49 AM Feature #4854: origin affinity: Ok. In this case you should create a branch or use the existing branch. I guess your changes are base on 3931a.
... Sergey Ivanovskiy
09:34 AM Feature #4854: origin affinity: Ah, that is. Yes, unfortunately there is no branch, only the diff. Galya B
09:33 AM Feature #4854: origin affinity: I did not find them because you did not commit them into the 3931a branch, correct? Sergey Ivanovskiy
02:49 AM Feature #4854: origin affinity: Sergey, you were able to miss this block of new code in the .diff?... Galya B
01:59 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: https://github.com/fingerprintjs/fingerprintjs changed their license and their current version is under commercial li... Galya B

10/13/2023

12:27 PM Feature #4854: origin affinity: Galya B wrote:
> With the introduction of cross-document messaging between the wrapper container and the iframe do... Sergey Ivanovskiy
09:36 AM Feature #4854: origin affinity: If @SsoAuthenticator@ related configs are not used, then all will go to the @"__default"@ key. If sso is enabled, dif... Galya B
09:34 AM Feature #4854: origin affinity: Good question. :) I modified the FWD code in @GuiWebDriver#init@ by adding at the end:... Galya B
09:27 AM Feature #4854: origin affinity: Galya, how did you test the new storage functionality? Sergey Ivanovskiy
01:07 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Refs #3931-457:
Greg Shah wrote:
> > Can we compile a list of authentication methods in OpenEdge 4GL that can be ... Galya B
01:05 AM Feature #3931: single sign-on for virtual desktop mode: Constantin Asofiei wrote:
> Galya, full reconversion is required because progress.g adds a new token - this invalida... Galya B

10/12/2023

04:55 PM Feature #3931: single sign-on for virtual desktop mode: > Can we compile a list of authentication methods in OpenEdge 4GL that can be applicable?
>
> I know only of @setu... Greg Shah
12:35 PM Feature #3931: single sign-on for virtual desktop mode: Galya, full reconversion is required because progress.g adds a new token - this invalidates token IDs in schema AST f... Constantin Asofiei
08:00 AM Feature #3931: single sign-on for virtual desktop mode: The *migration plan* should assess the production / live system and answer several questions:
# Is @/embedded@ mod... Galya B
03:39 PM Feature #4854: origin affinity: Sergey: Please review. Greg Shah
02:38 PM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: There are two issues:
first - there is no label on initial screen, the issue is caused by a ScrollEvent sent when FI... Tomasz Domin
10:26 AM Bug #7907: Browse row-leave handler not called after apply entry in FWD: Greg Shah wrote:
> Is this intended to be a generic bug or does this need to be moved into a customer project?
A ge... Yuriy Volyanskyy
09:36 AM Bug #7907: Browse row-leave handler not called after apply entry in FWD: Is this intended to be a generic bug or does this need to be moved into a customer project?
Is this related to any... Greg Shah
09:35 AM Bug #7907: Browse row-leave handler not called after apply entry in FWD: From Yuriy:
I made a unit test that works in OE but fails in FWD. Please see the attached file. It expects row-lea... Greg Shah
09:27 AM Bug #7907 (New): Browse row-leave handler not called after apply entry in FWD: Yuriy Volyanskyy

10/11/2023

09:55 AM Feature #3931: single sign-on for virtual desktop mode: Greg Shah wrote:
> > Virtual desktop and embedded use the same resource for the login page. It is overridden in hote... Galya B
08:52 AM Feature #3931: single sign-on for virtual desktop mode: > Virtual desktop and embedded use the same resource for the login page. It is overridden in hotel_gui to have the pr... Greg Shah
08:01 AM Feature #3931: single sign-on for virtual desktop mode: 3931a rebased on trunk r14770. Galya B
07:37 AM Feature #3931: single sign-on for virtual desktop mode: Constantin Asofiei wrote:
> * finish the sample SSO for Hotel GUI, and make sure it works for both embedded and norm... Galya B
06:32 AM Feature #3931: single sign-on for virtual desktop mode: Constantin Asofiei wrote:
> * finish the documentation: all new directory/bootstrap config options need to be docume... Galya B
05:17 AM Feature #3931: single sign-on for virtual desktop mode: Galya, I think 3931a rev 14791 is OK. What needs to be done before merging this to trunk:
* rebase 3931a
* finish ... Constantin Asofiei
08:09 AM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: Greg Shah wrote:
> Is wrapping even a valid ChUI use case?
I can't tell. But OE allows it. Hynek Cihlar
07:51 AM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: Is wrapping even a valid ChUI use case? Greg Shah
02:47 AM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: FWD after entering single character:... Tomasz Domin
02:15 AM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: 4gl - screen when fill-in has no characters... Tomasz Domin
01:47 AM Feature #4517 (WIP): optionally back the 4GL features for Registry access with the user-specific ...: Galya B

10/10/2023

10:14 AM Feature #4854 (Review): origin affinity: Solution attached as .diff based on latest 3931a r14791. Tested in Virtual Desktop mode (regular and auto login) and ... Galya B
05:28 AM Bug #7879 (WIP): Cursor isn't positioned right when FILL-IN split on multiple lines: Tomasz Domin

10/09/2023

04:47 AM Feature #4854: origin affinity: |WebSocket Event | Event Type ID | Description | localStorage access | Response WS msg | GuiWebSocket method |
... Galya B

10/08/2023

06:45 AM Feature #3931: single sign-on for virtual desktop mode: I've committed r14788 - r14791 with improvements to @fwd_sdk.js@: documentation on functions and an exposed @sendAuth... Galya B
01:01 AM Feature #3931: single sign-on for virtual desktop mode: The question is if there are customers using any 4GL methods like @setuserid@ for login page authentication: in-app c... Galya B
01:24 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: 4GL methods used by customers to authenticate in-app user & pass on login screens need to be provided in FWD for use ... Galya B
01:07 AM Feature #7884 (WIP): Standard 4GL methods used for login screen authentication to be exposed in s...: Galya B

10/07/2023

09:23 PM Feature #3931: single sign-on for virtual desktop mode: Galya B wrote:
> But when duplicating the logic from @ConnectionManager.authenticate()@, I've noticed that the query... Ovidiu Maxiniuc

10/06/2023

10:09 AM Feature #3931: single sign-on for virtual desktop mode: I imagine after merging 3931a, we'll focus on closing #4571 and #7067, and after that formulate the new requirements ... Galya B
10:03 AM Feature #3931: single sign-on for virtual desktop mode: Greg Shah wrote:
> I'm not opposed to doing this in the next set of changes (which have to be completed quickly anyw... Galya B
09:54 AM Feature #3931: single sign-on for virtual desktop mode: I'm not opposed to doing this in the next set of changes (which have to be completed quickly anyway due to customer d... Greg Shah
09:33 AM Feature #3931: single sign-on for virtual desktop mode: Can we compile a list of authentication methods in OpenEdge 4GL that can be applicable?
I know only of @setuserid@... Galya B
09:23 AM Feature #3931: single sign-on for virtual desktop mode: For this use case where the original code was using 4GL features for database authentication, I think we should imple... Greg Shah
04:02 AM Feature #3931: single sign-on for virtual desktop mode: Ovidiu, a little bit of context:
@SsoAuthenticator@ is an interface for implementation by the customer with custom... Galya B
09:45 PM Feature #3931: single sign-on for virtual desktop mode: I do not have a solution currently. Just some notes, until I read the whole thread and get a better understanding of ... Ovidiu Maxiniuc
08:36 AM Bug #7879: Cursor isn't positioned right when FILL-IN split on multiple lines: See the following test case. Run it and fill the fill-in so that the cursor wraps to the next line. Observe the unexp... Hynek Cihlar
08:34 AM Bug #7879 (WIP): Cursor isn't positioned right when FILL-IN split on multiple lines: Hynek Cihlar

10/05/2023

12:40 PM Feature #3931: single sign-on for virtual desktop mode: Ovidiu: Can you please review starting at #3931-430 and advise? With this task we are moving Hotel GUI away from 4GL... Greg Shah
12:35 PM Feature #3931: single sign-on for virtual desktop mode: P.S. @HotelGuiSsoAuthenticator.java@ seems to have to be placed in @embedded/src/com/goldencode/hotel@, but it will g... Galya B
12:29 PM Feature #3931: single sign-on for virtual desktop mode: I still don't know the answer of the last question, but what I can do on hotel_gui is done. The @SsoAuthenticator@ im... Galya B
06:22 AM Feature #3931: single sign-on for virtual desktop mode: I see @ConnectionManager@ tries to be smart and find the column names for user / pass based on @com.goldencode.p2j.pe... Galya B
06:19 AM Feature #3931: single sign-on for virtual desktop mode: The user password has to be encoded, the result is found. Galya B
06:04 AM Feature #3931: single sign-on for virtual desktop mode: I created a simple jdbc connection in the authenticator, but @SELECT COUNT(*) FROM meta_user@ returns 0. When is @met... Galya B
05:16 AM Feature #3931: single sign-on for virtual desktop mode: Where is the @meta_user@ table, where is the h2 db - the file @hotel_gui/deploy/db/hotel.h2.db@ seems empty. Is there... Galya B
03:12 AM Feature #3931: single sign-on for virtual desktop mode: For the hotel_gui authenticator there should be a connection to the DB and then @SecurityOps.setUserId(username, pass... Galya B
02:14 AM Feature #3931: single sign-on for virtual desktop mode: I'll do the review first and will keep the rebase when we are close to merge (as I assume it can be kind of difficult... Constantin Asofiei
02:03 AM Feature #3931: single sign-on for virtual desktop mode: Do I rebase and we do the final review?
Login / logout pages are not translated. That can go under #4762 or #7814.... Galya B

10/04/2023

01:27 PM Feature #3931: single sign-on for virtual desktop mode: I pushed small, but important fix for embedded handlers in r14786. To serve the hotel_gui login page as before, on to... Galya B
07:44 AM Feature #3931: single sign-on for virtual desktop mode: We're not removing @RemoteLaunchOptionRightsEditor@ and related code now, although it won't have any effect. I heard ... Galya B
06:28 AM Feature #3931: single sign-on for virtual desktop mode: Done in r14784. Galya B
05:38 AM Feature #3931: single sign-on for virtual desktop mode: Galya, go ahead and remove the @RemoteObject.registerStaticNetworkServer@ code for @WebClientLauncher@ in @StandardSe... Constantin Asofiei

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » User Interface

Activity

Activity

11/02/2023

11/01/2023

10/31/2023

10/30/2023

10/27/2023

10/26/2023

10/25/2023

10/24/2023

10/23/2023

10/22/2023

10/21/2023

10/20/2023

10/19/2023

10/18/2023

10/17/2023

10/16/2023

10/13/2023

10/12/2023

10/11/2023

10/10/2023

10/09/2023

10/08/2023

10/07/2023

10/06/2023

10/05/2023

10/04/2023