Name: Rocket ETX Customer Webinar
Uploaded: 2025-12-17T17:16:13.282Z
Duration: 59 min
Description: Rocket ETX Customer Webinar

Transcript for "Rocket ETX Customer Webinar": Ready. Hi, everybody. Thanks for joining us for this e t x ETX customer webinar. We're gonna be starting in just a minute or two. We're gonna give a couple of last minute people to join us, and then and we'll get going. Thank you. Okay. Why don't we get started? So thank you all for joining. My name is Rebecca Dilti. I'm a director of solution customer marketing for Rocket Software. We've got a lot of really great exciting content for you as well as a couple of including a couple of demos. I just had a couple of housekeeping things before I hand it off to the product team. First, we have q and a channel on your right. At any point in the presentation and conversation, if you want if you have a question, throw it in there. We're not gonna do q and a until the end, but I won't you are free to kind of add it as you have your question. We will be doing demos, and try to maximize your screen as much as you can, so that you can see all the details of the demos. There's some pretty cool stuff going on there. And right before we finish up the webinar, we will be, sending you a survey to just get a feel for what you thought of the content, the presentation, the speakers. We'd love your input, because we want to make sure that these events that we're holding for you are beneficial and productive and helpful to you as you, use, ETX and whatnot. So, and with that, I am going to hand it off to Hernando. Thank you, Rebecca, and thanks everybody for joining us today for the launch of ROCCAT ETX-twelve 54. We have a couple of people with me, Eric Marakin, who's a solution engineering, Brian Tam and Nathan Kidd, from the, r and d group that are going to be doing the demos. Before I get started, just a quick reminder that anything that we say today, especially forward looking statements, are only for your information and are subject to change. Of course, if there's any change, we will inform the public. Other than that, you know, that's that. And let's go on to the agenda. We're going to start with a brief introduction about ETX, although most of the people here are already familiar with it. So I'm going to go quickly over that. And then we're going to look at the key features and themes in ETX twelve five four, followed by demos of the single sign on and multifactor authentication as well as security key redirection. And we'll close with some resources that are at your disposal for interacting with us as you use ETX. So let's start with an introduction. And the first thing that I'm going to go talk about is Rocket's motto of modernization without disruption. So probably most of the people here have not been with Rocket for a long time. And for those of you that you're new to Rocket, our business supports organizations worldwide to modernize critical business applications. And in that context, ETX provides a platform for remote work, for computing environments and travelization. We at Rocket C, ETX is a tool that is key for IT organizations that support engineering teams as well as other teams that require access to high performance graphics and compute hardware environments. And part of, why ETX and we see the importance of ETX is we're also making some shifts into our products structure. I have not interacted with most customers, but now I'm starting to get, you all. I am your new ETX product manager. Given the importance of the product, now we have a dedicated, product manager for ETX. You probably you are familiar with Chris Law, who's done a great job and whom I speak with daily. But now Chris was supporting multiple products, whereas I'm going to be dedicated to ETX. If you have any questions or any comments or anything that you want to know about ETX, please reach out. My information is going to be at the bottom in the resources. Now let's jump a little bit into, just briefly, the reason for ETX. Know, I'm not going spend time here, but the notion of remote work and remote connectivity through applications and desktops is not new. We've been using it for a long time. But not every use case is the same. The use cases that you use daily are things like Microsoft Office, remote desktop for Windows, etcetera. But there is a class of applications that require high performance graphics and access to high performance computing resources, and those are the scenarios that ETX really favors and supports. ETX specializes in geographically demanding solutions. And it really provides the platform for collaborating on a secure environment where you protect your IP, are able to communicate and collaborate with your teammates with an experience that is a key or very similar to an experience of working on your local desktop machines for this type of any class of applications. Let's move on to the next one. In terms of, you know, what we provide with DTX, provide a web based application that enables you to launch both Unix and Windows desktops. And and like I was saying, it provides you that seamless experience. There's many more features in here that I'm not going to go through because most of you are already familiar with the tool. But what it provides you by allowing you to support a centralized environment is cost savings in the terms of reduction of the resources that you have, being able to share those resources, administer them in a central place, and provide that ability for employees to work remotely for anywhere they are. Provide that compute power that they need to perform their engineering design and other, you know, compute intensive tasks, as well as protect your IP. Because with your IP being in a centralized space, you can have the the ability to protect that IP as opposed to have that in desktops and exposed to maybe, you know, security issues. So now I'm going to jump to talk about 12.54 and what is common in 12.54. There are two broad teams in twelve five four, where we focus primarily on performance, scalability, and new security capabilities. We also released we also are releasing fixes for a number of bug fixes and feature requests that are coming from UR customers. And we're gonna look at some of the details of what is done in ETX, starting with the new ETX twelve fifty four authentication server. Before I jump into feature, I wanted to really stress what's the importance or why do you care about SSO and MFA. As companies harden access to applications through centralized identity management, MFA and SSO provide a single authentication platform to access systems, third party applications, such as Office three sixty five. You know, what's changed the landscape of your access to applications and systems is changing. And nowadays, we don't have, any more centralized access to applications that are installed, whether it's on my desktop or on my computers, you know, in a in a data center. They could be anywhere. They could be in Microsoft data center or in Google data center, still having that ability to have a single identity management that not only allows you to access all of those applications, but provide a secure environment for doing that through the secured identity provider management. That that is the key for that and why it's so important for us and why we are in December releasing a new authentication server that provides native support for single sign on and MFA. It replaces the support for single sign on through OTDS or OpenText Directory Services as that source of SSO and MFA. And along with that, we're also introducing the redirection with security keys. We'll hear more about that, when we start before we jump onto the demo. It allows you to use security keys with, from your local desktop with ETX. The second thing is really on performance. And there's many things here, you know, including, reduced memory footprint. We have new APIs that have been optimized with our adjusted, numerous settings. But one of the key things here or one of the key features that we provide in 12.4 is we have improved the scalability of the platform to support over to 20,000 nodes in a single ETX installation. Some of the other key things that we are releasing with performance related to performance are the support for the AV1 codec for high performance encoding of video. And we've also optimized the AV1 codec to work with NVIDIA and AMD GPUs. And lastly, we've also introduced the support for ARM 64 architectures for the ETX server. It was already supported in Windows, but now you can also install the server on ARM64 architectures. So with that, let me jump on to the last part in terms of updates. As I mentioned, we have a number customer issues that we have fixed and introduced in twelve five four, including 44 box fix and 43 new feature requests. If you want to learn about everything that we've done in terms of those bug fixes and features. That information is available in the December release notes. We will provide links to the documentation and the release notes in the resources, and we'll publish those in the new ETX forum, which you'll hear me talk about more shortly. Now, a couple of other announcements that I want to make sure that is that everybody is aware of. I mentioned the new ETX authentication server as a new feature in twelve five four. In twelve five four, although it is still supported, OTDS is deprecated. So what does that mean? It means if you have an installation of twelve fifty three or a previous release that uses OTDS, it will continue to work with twelve fifty four. But I would encourage all, you know, each of you that are using OTDX with ETX to start planning for migrating off of OTDS. You can just install 12.4 and start using it, but start planning. And more importantly, if you can reach out to us if you are using OTDS, because there's a couple of things that we want to discuss with you as well on that. We also had to discontinue support for Oracle Solaris on the ETX server, and I wanna be clear about this. It's only on the ETX server. If you have ETX nodes that are running on Solaris, those will continue to work. The reason that we had to discontinue the Oracle Solaris platform for the server is that we have some issues with compatibility. It doesn't support the latest versions of Java that is the the language platform for ETX. So we had to discontinue that. You will no longer be able to install 12.4 on SLRX platform, again, for the ETX server. So that wraps up the feature part, and now we're going to jump into the demos. So we're going to start with the SSO and MFA. And for that, we have Eric Marroquin, our solution specialist, that is going to walk us through that. So Eric, please take it away. Oh, and sorry, I stopped sharing too soon, so let me get back to Not a problem. slide. Thank you so much, There. you are. Appreciate it. Hello, everyone. As Hernando mentioned, my name is Eric Marroquin. I'm a senior solution consultant at Rocket. I will do a live demo of the ETX ops server that is available with ETX SP four, and then we will cover interacting with Azure Entra ID. What you see here in this slide is a kind of brief outline of what it is that happens when a user is connecting with ETX and utilizing our new authentication server. So first step is, you know, end user connects to ETX, providing URL to connect. If ETX is configured with our authentication server, the login then gets redirected to that authentication server. User will get prompted by whatever identity manager corporate has set up with our authentication server. This could be, as an example, Okta or Azure Entry ID as I will cover in the demo. The user then provides credentials, gets prompted potentially in a mobile device for a PIN. User could potentially also get redirected to other push approval MFA applications such as MS Authenticator or, you know, Symantec VIP to mention a few. And once, of course, the authentication is successful, the end user lands on the ETX dashboard and will have access to the ETX node to run, you know, whatever applications are pre configured for that user. I will cover that demo shortly. And in the interest of, you know, being able to show this demo without any potential problems since we're having some choppiness in the session, I will stop my camera actually and just concentrate on the demo when I share my screen. Let me do that right now. I'm gonna grab the screen and just disable the camera for a bit here. Excellent. Thank you, Fernando. Please let me know if you're able to see my screen. We can see it. Excellent. Thank you so much. So as you can see here, I have just a a browser, and, actually, I'm mirroring my phone too so that you see that interaction, that workflow when I connect. And the first thing, of course, is, you know, I'm, you know, typically accessing through whatever corporate browser I have. I will have a URL that will get me to my ETX dashboard. Of course, it configure with the authentication server. I click on that link, and immediately what it will do is it will prompt me for my corporate credentials. So I will enter that information. I click next. It will prompt me for my credentials here. And as you can see, then I'm set up now to receive a code via SMS. So I click on that, and that's the way that I've been set up. And I get my code right here on my phone. So all I need to do is just grab that code, enter that here. And click verify. And depending how your, you know, authentication options are set up at corporate, now you may get a push option into, some other solution that corporate may support. In my case, for me, I have MS Authenticator. So I go to MS Authenticator, and I need to validate that. I'm going to authenticate and make sure I have access to that. And all I need to do in this case is just simply enter an ID there, ID, and say, yes, this is me trying to gain access. And, of course, you know, I need to provide access to that device. And I'm going to say yes. I'm going say don't show this again because I want to have it if in case I need to revisit it throughout the session. And click on yes. And I automatically land on the ETX dashboard. And whatever profiles are configured for that individual, I have access of that individual right now. So what I'm gonna do is I'm gonna click on a couple of them. I have one simple one here that will launch an extern onto a back end server using Entra ID. It will authenticate me automatically. It's prompting me whether or not I wanna go through the web client or the native client. This is a configuration option that I've set up. I would say always for this instance. And it should connect me. I will make this a little bit bigger just to, you know, make sure that you're able to visualize it. I'm on a large four k monitor, and I I I get sometimes the fonts don't quite show the way that you would want. So as you can see, if I type environment here, it recognizes me as that user, you know, a rocket software. This is a Linux Ubuntu server that I'm connecting to. And, of course, not only I can launch the specific application, but if I want to, of course, I can launch my desktop of choice. In this case, I've configured XFC, but it could be anything. It could be GNOME. It could be MAIT. It could be whatever is the standard. Again, I wanna try that with a native client, And it automatically authenticates me and it brings me to my desktop. I've set up a specific resolution already for this. I, you know, can open my applications, large, and you'll see that it is, you know, the same individual here that it is connected. That is, you know, in essence, what you're able to do. I'm able to, you know, access any application that is already preconfigured for me. As you can see, once I authenticate, I'm able to interact with my applications in my dashboard. I could close the browser and automatically be able to, you know, log in into that again. We support SSO. I don't have to pass my credentials and my sessions are there. That pretty much covers just the basic, you know, configuration and interaction that you do with a typical identity manager. Fernando, back to you. Great. Thank you, Eric. Great. We have a second demo that Nathan Kidd from our engineering is going to be showing us. But before I hand it over to Nathan, I wanna talk a little bit about, you know, what this feature is about. So, of course, we have remote environments, so you have less access to things that are physical on your computer. So this is really about the that ability to redirect and be able to access a physical security key, like Nathan is gonna show you, to do, interesting security, things. And there's a number of use cases. The use case that Nathan is going to demo is the OpenPGP signature verification to verify assets that are committed into a Git repository. But there's other features such as, doing, a web auth and authentication or use your security key to be able to authenticate to a back end system that is accessed through ETX or other things like being able to sign files, emails, and other assets using OpenPGP to make them tamper resistant using a security key or other things like encrypting the files. So it's a really cool thing that really, you know, provides that tight integration between your local desktop and the remote systems that are accessible through ETX. And with that, I'm going to hand it over to Nathan. So, Nathan, please take it away. Hello. My name is Nathan Kidd. I'm a developer on the ETX team, as Hernando said. Let's look at how ETX can forward your local security keys to remote sessions to help your organization's security. When I say security key, I'm talking about something that's usually like this, a physical device. This is a YubiKey. In this simple example, we're gonna demonstrate a developer signing a git commit using the security key to create a verified change in the organization's code. I'll share my screen here. This is a Windows desktop, And let's just think of, the problem we're trying to solve with this. If we look at this test GitHub repo, and you could put that URL in your own browser and see the same thing. We have Santa's naughty or nice list, and Hernando and I are doing well right now. But suppose there's the mischievous elf, doesn't like me too much, says, wants to put me on the naughty list and does a little bit of slate of hand. He commits this, he pretends to be Santa. So pushes this change. If we go back to that website, which, again, you could see in your local browser, I'm no longer nice. I'm naughty. So this is our our our problem here that we see this change, and it looks like Santa did it. How do we know if it really was Santa or was this mischievous elf? So to solve this kind of problem, ETX supports forwarding your security key to a remote session, and we'll look at that now. This is the YubiKey, manager, and right now there's no key inserted. When I insert it, you see it shows up. And we note that it has a unique serial number ending in 42. There's also a certificate installed that we can use for authentication. Meanwhile, in our ETX session, we have a profile under advanced devices. We have smart card forwarding enabled. If we go to that session and we wanna look and see is this smart, security key available, we can say GPG card status. And you'll notice that it's a YubiKey here, and it's the same YubiKey with the same serial number. And we also notice it has a certificate ending in EFA1. We can do hot plug support. Right now, we see on Windows, this thing is plugged in. If I unplug it, it disappears here in the remote Linux session. If I try and do card status as there's no device, I can plug it back in. It shows up on Windows, and when I attempt to use it in the session, it's back again. So let's fix the damage that this elf did, but do it in a secure, verifiable way. Put me back to NICE. This time when we commit, we're using this dash s command, which means sign. And you also notice that I'm telling the GPG agent I want to enter the PIN on the TTY. So we run this, and it does, in fact, ask for a PIN. So this is asking for the security key in front of me to verify the PIN. We do that, and that happened really fast, but all of the magic happened right there that git talked to the GPG agent, which talked to ETX, which forward a conversation from this remote Linux system to my local Windows laptop where the physical security key is plugged in. We can see the result of this. Here's the change where the fake Santa, the naughty elf, changed me, and we couldn't verify who actually made the change. Here's the change we just made now, switching me back to nice. And you'll notice that we have a GPG signature, and it includes the RSA key, that e f a one that we noted. If we push this up to GitHub and then go back to our browser and we refresh, you'll see that I'm back to nice. And the critical thing we'll note is that this change from the the elf pretending to be Santa doesn't have this verified, but the change we just made now with the security key has this verified button. And we can note that the change itself was signed with that security key and that certificate. So that's one example of how ETX forwarding security keys can help your organization's security. Fernando mentioned there are a lot of other uses for security keys. Check our documentation for exact, capability and platform support. But back to you, Hernando. Thank you, Nathan. Really cool. Let me get back to sharing here. Really cool, and I hope you all enjoyed that great demo that both Eric and Nathan did for us. So we're going to wrap up here with a few resources. The first thing that going to mention here is the roadmap. Of course, the third column here is twelve five four, which is already released since November 18. And you can is available for download for anybody that's under maintenance or buying the product, buying new licenses of the product. But then we have what's coming up in the next year. And one thing that I wanna mention is we're in the process of kind of reviewing how we do releases going forward. We definitely will have at least one or possibly two service packs in 2026. So we may have a 12 by five and a 12 by six. We're also evaluating what is the content that is going to come out for that, as well as what's going to be the schedule for hot fixes that we'll provide to to you for anything that you report going forward. So more more information to come up on that, you know, as far as how the schedule is going to be for releases. Terms of content, there there are a few key, pieces that we're evaluating for December and December, including, more support for WALAN. We didn't really mention that in content today, but we started with a first level of support for WALAN in 12/1954. So it's available for customers that are using Linux 10. You can use Wayline, of course. Nowadays, very little applications are using instead of X. So it's kind of more nominal at this point, but we will continue improving that and add additional support in the upcoming releases. Other things that we're looking into is more into containerization. That's another one of those that we started doing some prep work for December. Of course, when you move to a containerized installation, you will need to have something that is reentrant. So your your container the installer, you know, that container is not going to have an interactive installer because that will break automation. We've done, in December, we introduced some scripts that are completely reentrant and can be scheduled from a command line for a command line installation with containers. So in theory, you could install ETX in twelve five four into a container, but it's not fully packaged as a container. So we'll continue improving that in the upcoming releases. Then from an authentication server, there's a couple of new things, and I've I've already seen a couple questions. So this may answer some of the questions. We'll we'll go over those again at the end. But from an authentication server, you heard me talk about the configuration being command line only in December. In twelve five five, we are going to introduce a UI for configuration. The other thing for people that are going to have already installed and configured a number of profiles into ETX, of course, you switch to Okta or Entra IDE or you switch from OTDS to Okta, then you're going to have to make sure that your users continue to work. The good news is that in the profiles, all of that is virtualized, so the users are not directly referenced by the user ID but by UUID. What we do not have yet in twelve five four is the ability to map those users. We are working on scripts that will allow you to do mapping of users when you do a migration from your existing identity provider to one that works with all of, you know, all of or any of the other protocols for identity providers. So that's so for example, if I'm user h borda in my local Linux system, then as I move on to Okta, then I would have to map that h borda maps to hborda@rocketsoftware.com in Okta and that kind of thing. So those scripts are coming up in one of the upcoming releases. We're working on those as we speak. If you again, if you're using OTDX or if you would like to do a migration, let us know, contact us, you can contact me or contact support, and we'll engage in a discussion with you. I think what we would like is that people start using twelve fifty four right now, and then we can plan on those migrations as we go on from here. What else do we have? So another one of the we've had a couple of conversations with customers already, where they're telling us that one of the aspects of the platform that they really care about is being able to observe or being able to monitor what's going on in the platform all of the time. So I want to know, for example, what the latency in my network, or I don't wanna know any of your all the aspects of how well my platform so that verges into observability and telemetry. We're early days right now, but that's one thing that we're looking at expanding our monitoring capabilities beyond what you can do in the ETX dashboard to a more robust observability and telemetry platform, such as something like OpenTelemetry or any or or another one of the the OpenTelemetry or the telemetry platforms. So that's some of the aspects that we're looking for our upcoming releases. If there's any features that I didn't mention or I didn't cover here and you're interested, feel free to reach out to us and let us know what other features you would like to have in our upcoming releases. And as I mentioned, we'll provide more details about the roadmap for 2026 in the upcoming weeks. So that wraps up the content of this. The other kind of topics that I'm going to go before we switch on to questions is available resources to you. One thing that you're going to hear me already mention a couple of times is we just launched this last week, we launched a new ROCCAT forum. And I'll say a couple more words on that, but that's really important. I want to put it out there for people to sign up to that broken forum for having that community. We also are going to publish the webinar that we're recording today. It's going to be available on demand. Updates and instructions on how to view it are going to be available in the forum. And for those of you that registered and are with us today, you will also get an email telling you how you can rewatch it into the on demand. Along with that, those instructions to watch the webinar on demand, is going to be links to the product documentation and release notes. Actually, a link to the forum as well as the link to the docs is available right now on the webinar. If you go next to the Q and A to the docs tab, you will find links to the forum and the twelve fifty four documentation in the documentation portal. And other than that, you will also have access or you will have links to access the Rocket customer community, which is our portal where you can get product downloads, access to knowledge articles, access to support, and more additional resources there. So that's some of the things that you will have available after today. All of this information is going to be available to you in the forum. My contact information email is h for the rocket software dot com. You can send me email. You can contact me on the forum, and we can have a private conversation in the forum, or you can just, you know, post post questions in the forum, and we can interact and introduce each other over there. As well as the email for customer support is support@rocketsoftware.com, or you can go through the RCC for development access support or in the Rocket website. There's also links to that. That is the resources that, we were going to share today. A couple more things. If you have new users, that have not installed their experience or use ETX, We also have ETX live at rocketsoftware.com where we host ETX, and you can just go use it and experience, you know, how, responsive it is and, the collaboration features in there. So that's a resource that's available for new users to experiment with ATX without having to go through all the installation. And finally, wrapping up, the forum, as I mentioned, is at community.rocketsoftware.com. We, encourage you to join us there. We want this to be a thriving community where our users can interact with each other, share tips. You can also interact with the Rocket experts in there, both the support and all the folks from engineering will be there to answer your questions. I will be there in the forum to monitoring. And if there are questions, I will be monitoring and answering those. But I mean really we want to make this a thriving community. For example, we will share announcements about product releases. If you go to the forum right now, you will see that there is an announcement about twelve point four. As we release hotfixes, we will mention those in the forum. So you can subscribe to the forum and get notifications when a release is available. And you will have information about other things like knowledge articles and public information as well as really the ability to collaborate and communicate with people at Rocket as well as with your fellow ETX users that are out there in the community. So this wraps up the content and we're going to now move on to the Q and A. So thank you all so much for participating in here, and I'm going to open it up for Rebecca, who is going to tell us a little bit about the questions in the Q and A, and is going to tee us off for that. So Rebecca, over to you. Yeah. Thanks, Fernando. Just to reiterate, if you go into that docs tab on the right next to where it says q and a, it says docs. There's a direct link to the forum. Go sign up right now as we're talking. There's also a link to the docs portal. So the docs portal has all your technical release notes and installation information. And then the, the RCC, so that's the ROCCAT customer community is your dashboard where you download your files, right? So that's where you get the latest and greatest December. So with that, I'm going to start we've got some great questions in here. So I'm just going to start asking them, exceed TurboX twelve fifty four monitoring can be managed from any external market monitoring tools? Hernando, did you want to take this? Nathan, is there something Nathan, or is there anything that you have to share? Before before you guys jump in, so although Nathan and Eric are extremely knowledgeable, there may be questions that they don't know. Now if we cannot answer to your questions right now, we will follow-up over email, with you. We will capture who asked the question, and we will, we we will reply to you after the meeting. But Nathan or Eric, is there anything that you can comment? I think we have auditing, tools, but if you're thinking about, like, large scale performance or just session information, we don't integrate right now. It is something that we are looking at, and we would be interested in what tools you are using and if you have existing systems. So we would definitely like to hear from you on what you would like from that. Great. Thank you. Okay. Next question. With ETX authentication server, is there the ability to map SSO user accounts to Linux? That is so let me take that one. That that is the feature that is not yet there in the product right now. So right now, if you if you would like if you already have the product configured and you have users, then it would work if the user IDs are the same. For being able to do migration and do mapping of users, we are developing additional scripts. So, for for that, I mean, you can install twenty five four, use it with your current, with with your current authentication mechanism. But to adopt and migrate to a new authentication server, you'll have to wait, for a little bit. Okay. Next question. So he's asking the authentication server is a standalone server unlike ETX license server, and can it run on the same host as the actual ETX servers, or can it run-in some mode? I can answer that one, Rebecca. So this is Eric. So the ETX authentication server, as you saw in the demo, as it is released in SP four, should be installed on a separate Linux server, if at all possible. Of course, that is up to you when it comes to how you deploy your infrastructure. In the demo, actually, just to save for the number of VMs that actually have to utilize, I have the ETX web server and the ETX authentication server on the same host, and that's quite possible. But if you have a large organization, there is a lot of users, then you're putting a heavier load on that system. So our recommendation would be that, you know, for any type of implementation where there's a large amount of users, authenticating and gaining access to ATX through the authentication server, that you deploy it on a on a separate VM or physical machine to be able to support that infrastructure properly. Okay. Next question says, can we convert login ID from email address to only the username without the domain while transitioning into the ETX session? So that is the same question that we answered before. That's user mapping, and it's common in release down the road. Sorry, apologies. No worries. There's questions about requiring a database for authentication, know, such as OTDS requirements. Yeah. So in the background, Right. I I asked the the developer what's happening there. He said, no. No database. There is a caveat that OTDS did partitioning of users and groups that authentication server does not. That's why it doesn't need a database. But the short answer is no database. Okay. And then there's a question around is this possible is it possible to initial I think it's initiate server sign on with SSO with assure ID. So the answer to that is yes. That so our shared ID is is now renamed as enter ID, Microsoft enter ID. And that was the demo that I did. So and you can see that as I try to authenticate again and I open the browser again, Once I authenticate it you know, you could have done it early in the morning. Once you authenticate and that authentication has taken place successfully, you don't need to enter credentials anymore. So, hopefully, that answered that question. Great. Okay. Next question. These are all really great questions. Thank you for sending them in. Will the security keys work with RADIUS key authentication? Nathan, you wanna jump in? Yeah. On the Linux side, we support the standard PCSC protocol for accessing these security keys. It's, in fact, PIV mode. So if RADIUS is using that standard protocol, then we expect it to work, but I have not actually tested it, so I cannot say for sure, yes, it works. It would need to be tested. Okay. Next question is around migrating from 1253 to 1254. Can they do it with patching? Yeah. I mean, you can just install 1254, as the you know, on top of, +1 21253. Okay. So and then the the follow-up to that was they don't see patches available in the download section. Does that mean they just download twelve five four itself? I believe so, but I don't know. Eric or Nathan, do you know? Correct. Yeah. All all you need is +1 254. Even if you had a +1 251 or 12 50, 1254 is inclusive of all the previous patches, and all you will need would be to be able to install twelve five four. It is available for customers with maintenance to to download. Once you install that, you will see the option to be able to work with the authentication server. Of course, the authentication server is a different installation package that you can also access from the Rocket website. Great. So I'm gonna, we're starting to run out of time and I wanna make sure we have enough time for the survey at the end. There's a bunch of additional questions on feature and functionality. We will be adding more content to the forum and diving in there. That's also a great place to ask questions around, you know, net new enhancements that you'd like to see. One of the questions is around the telemetry feature in 12.55. Is there any additional information available now? And if not, you know, do you have a timeline on when they can read more about it? We'll capture, don't know who answered that, but we'll follow-up offline on that to engage in our conversation. It's early days. Okay. Another question on kind of migrating from earlier versions like twelve five two to twelve five four. How involved how much of a project is that for customers? Hey. I can take some of that if you want. I don't know if Nathan wants to pitch into, but it it really depends on, you know, how it is that you wanna plan your migration from earlier versions of ETX to twelve five four. If you wanna implement the authentication server and you're planning to, you know, interact or configure with identity managers like EnterID, AWS, or some other type, will be more involved. It also depends if you want to migrate in place sessions, meaning if you have an older version of ETX and you want to allow users to continue to run their sessions, then upgrade to twelve five four, configure the authentication server, and then, you know, coming Monday, you know, as you implemented this, let's say, as an example, over the weekend, have the users automatically map the how live sessions running or suspend the sessions running and be able to gain access to that. For that piece, we are in the process. That will be upcoming when it comes to, you know, migrating live sessions in that sense. But if you chose a path in which you wanted to take advantage of downtime and all the users are, you know, exiting their sessions, you can do then an upgrade, configure coming Monday, you know, all users will start a new first session with a new authenticating mechanisms, you know, whatever they may be with the authentication server. Then that would be a more simplified type of approach. But it really depends on, you know, how it is that you wanna do this and what what it is that you wanna achieve. Yeah. I would just add that, again, the super simple case I have created, it was five minutes, but I don't have all these users with live sessions. It depends on. install complexity for sure. Okay. We've got a bunch of questions around the authentication server. So one is, does it need to be installed on a cluster two or more VMs when used on a large scale similar to OTDS. Yeah. The recommendation would be that you will have some redundancy because that becomes your single point of failure. If the authentication server is not working and that's your mechanism now to be able to, you know, interact with EntriteD, with Okta, or, you know, anything else that you configure it for. Yeah. The the recommendation would be that you have some redundancy. So you will need, at the very least, two of them implemented. But just to be clear, it doesn't need to be installed in a cluster. It's just a recommended best practice for, you know, high availability. Okay. And there's I'm gonna do two more questions, and then we're gonna run to go to the survey. One is around, can we configure the authentication time so that users are forced to do authentication after a timeout? I can take that. I mean, at least from my experience in configuring this with Okta and with Entra, that is typically set by, you know, whatever back end you have. I don't think we have from at least what I can see, I will verify and double check with our admins and our developers if there is anything within the ETX authentication server to set those parameters. But typically, that is set up by the back end directory services or the identity management solution. In my case, when I, you know, work with EntriteD and I went through all of this configuration, after, I would say, probably an hour or so, I will have to re authenticate again. So it seems that, you know, the authentication period had time out and I will need to provide again my credentials if the session was left idle, at least in my experience. But I've never set up anything with the ATX off server for that specific period of time. We'll verify, though. Thank you. Yeah, okay. One more question. We have, we're not gonna be able to get to everyone's. I appreciate we will get to you after the webinar if we didn't answer your question in person. Last one is SSO and authentication server can be implemented after applying SP4 so we can have a transition to SSO later. Absolutely. Yeah. Absolutely. I mean, we you do not need to the the the new authentication server is not a required component of twelve five four. You can install 1254 on 12/12/1953 or 1252 or a previous release, and you can later on roll out the authentication server at your convenience. And that and that that's probably something that you want to consider planning, you know, making that move in a planned way. So if you if there are other features or fixes that you have that you need from twelve fifty four and you just wanna take benefit of those, by all means, you can just install twelve fifty four and start getting those and then do the authentication server down the road. Great. So, thank you so much for your time. I think this was a really great conversation. We got some exciting. stuff that we shared with everybody. I'm going to launch the survey. Again, this is just three questions. It's to get some feedback to make sure this was helpful to you, that the presentation was good, that the content was valuable. We'd really love you to, fill out that now before you drop off and give us feedback. And also before you leave, go into that Docs tab and click on the link to the new forum and sign up. You have to also not just sign up as a member, but also sign up for notifications for the forums that when Hernando posts something you will get a notification that it's available. So you all for great questions, great interaction. So I hope you enjoyed it as well. Yep. Thank you so much for attending. Appreciate it. Yep. Thank you, everyone. Thank you. I'm gonna give you thirty more seconds to answer the questions before I close the survey. And feel free to drop off once you finish filling out that survey. And we'll be sending out the recording after and after we're done probably sometime tomorrow. And then we'll also be posting the recording in the forum as well. Okay, a couple more seconds. If you could finish up with the three questions, that would be wonderful. Thank you again for your time and have a wonderful holiday season. Okay. I am going to close it out in I think it's gonna give me a ten second thing. Closing thirty seconds. There you go. So you got thirty more seconds. All right, ten more seconds for the survey. Thank you so much. Have a wonderful holiday. We'll be in touch next year for sure with more exciting stuff from Hernando and the team. Okay, thank you. Thank you all. Bye, bye. y'all. Take care, everyone.