Name: Rocket Customer Webinar: OnWeb Web to Host Lifecycle
Uploaded: 2025-09-09T17:31:23.300Z
Duration: 56 min 52 s
Description: Rocket Customer Webinar: OnWeb Web to Host Lifecycle

Transcript for "Rocket Customer Webinar: OnWeb Web to Host Lifecycle": Hello, everyone, and welcome to today's webinar. I am Evan Tackett. I'm the solution marketer looking after Secure Host Access and our whole stable of terminal emulators here at Rocket Software. I am excited to be here. I think it's an exciting session, and I'm joined by, our principal product managers, Barbara Ballard and Chris Wall. Before we get started, I'd just like to say that we really want this to be an engaging session, an informative session. So if you have questions, if if there's something that doesn't make sense or, burning question, Go ahead and send it along in the chat or the the q and a panel, and I'll make sure to raise that to our speakers, and we can get a an answer for you right away. But with that, I think I will go ahead and hand things off to Chris to get us started. Sounds great, Evan. Hello. I'm Chris Loll, and happy to be with you today, and we're gonna talk about the agenda next. So speaking of, all those terminal emulators that Evan was referring to, we're gonna give you a first a little historical background on the terminal emulation host access industry and the products associated with it so we get on the same page with regards to really what we're talking about here. To begin with, we're gonna look at what the path forward looks like with our new secure host access product. We've got a new product life cycle. We wanna share the details of that with you. We wanna talk about how we're gonna help you, you know, go through this upgrade migration process over the next few years to Secure Host Access and what commitment we are, you know, showing and having for you. And, of course, we'll do questions along the way and or at the end of the presentation. Alright. So first, we're gonna do a disclaimer before we do anything else. This is the most exciting part of the presentation. Basically, this is something to say that a lot of the things we talk about today are forward looking. They're gonna happen in the future. Things could change, market conditions, company conditions, etcetera, and that could impact, you know, ultimately what happens with our plans here, but we're trying to be as transparent and accurate as possible, and, just, you know, just beware that things could change. We appreciate your, your flexibility and understanding. Alright. So historical background. This is an interesting look. Some people see it as an ant farm or or, hamster tunnels, but, really, what it is is it's a, illustration of our corporate journey. Barbara and I have been in this industry for, pretty much ever since we were kids. We started a detachment many, many years ago, but, this really just shows kind of how the terminal emulation industry grew, has grown, and and has and grew over the years to where we are today. So, just real quick. So you've got, you know, Barbara and I started AttachMate. We merged with WRQ. We joined, Micro Focus at about 2015. That's when the portfolio kind of came together. That includes, the OnWebWeb to host product. Then we had, the merger with OpenText in 2023 and then, again, here at Rocket Software. And, you probably recognize a lot of the, you know, merger acquisitions, the brands, the company names, and so forth. You probably used, you know, one of these terminal emulators in the past, one or more of the terminal emulators from one of these heritage companies in the past. You probably have a similar sort of, illustration that you could draw, you know, with your company and how many merger acquisitions you've had. But this is kind of, you know, our story and, and and our history. And we wanna share that with you so you can kinda see kinda where you came from and then kind of where we're going going forward. And the going forward is with Rocket Software and with the secure host access solution. And with that, let's turn it over to Barbara to talk about Rocket's values. Alright. Well, thanks for that, Chris. And he's correct. We have been around for a long, long time. We started to do the Attachment, We'll just say quite a few years ago. Chris and I have both been in the terminal emulation space for a very long time. So, so I think we kind of understand your business, and we understand what you're doing with terminal emulation today. But what we're about to talk about is a new product that we're launching, although it is, it's based on existing products that came out of Micro Focus. But it's just it's a whole new conversation. It's a game changer in my opinion. It it adapts to the things that are emerging in the market today. But before we talk about that, we wanted to talk a little bit about Rocket. And I actually asked for for this to be included in the presentation because this is kind of a message from me to you. You've been through a lot with us. Right? You were with Micro Focus for a long time, and then, of course, we just took a period of time there that didn't seem very long where we were with OpenText and now we're with Rocket. And what I want you to know is because under the Rocket umbrella, we brought customers from the OTAMC. That's how they referred to it, divestiture, which is really all about terminal emulation, and our customers, the products, and the employees. And we brought those all over to Rocket. And so there's a lot of change there. And as Chris and I said earlier, we've been through a ton of change. We've been through so many different, mergers and acquisitions. Some are good. Some some, you know you know, maybe not quite as good. But what I want you to know as my customer and even as me, an employee, you are in a great spot with Rocket. Rocket has a customer focused persona. They really care about what you do every day with your products. How can we make them better? How can we do things in advance to make sure that we're already offering you features and functionality that you're gonna need when you get there? And they wanna hear your feedback. So that's really important to me because that's kind of my mantra as a product manager. I really believe that the closer I get to you as my customers, the better my products that I manage are going to be for you going forward. So, so you're in a sweet spot. It's, you know, it's only been I think I counted this morning. I think it's been seventeen months since we've been with, Rocket Software, and I don't know how much of the love you're feeling. And it sounds a little silly to be talking about love, but it really isn't. I I will tell you probably what for one of the first times in my thirty year career, Rocket Software really walks the walk. They don't just talk the talk. So they really do value your business and our relationship with you, and I do as well. And so we're hoping that this is really a good spot for you to land as as my customer and for me to land as an employee. So so with that said, let's kinda take a look at what is going on and what we are calling our path ahead. So hopefully, you can relate to the slide. I'm not a salesperson. I'm a product manager. But this slide really kind of presents to you some of the current statistics brought to you by some of the market leaders about the security landscape and the things going on in the market today, which is why we're changing our trajectory, if you will. So, so terminal emulation has to be brought into the enterprise security landscape, because of these things that are listed on the screen. One of the things that that I highlight when I talk about these statistics is really the top middle bullet. This ability for ne'er do wells to get compromised or stolen credentials to access an organization's system of record. That is really the bottom line here. That is we have to change that game. We cannot continue to have year over year increases where these stolen or compromised credentials are used against you. And, you know, I am not so egotistical to think that that's an easy change for you. Right? There is nothing in the security game that is easy for you to implement or respond to, but we, as Rocket Software, wanna make some decisions on your behalf that will help you, put more layers of defense. That's really where we're going with our new product. But it's it really does come down to where we are in the security landscape. I mean, if you look just over the last twelve months, just the amount of change, the breaches that are happening, the the, I mean, the cost of a breach, it obviously is gonna go up. But the amount of credentials that are being, compromised, the the amount of information that is given to somebody who shouldn't get access to it based on those compromised credentials, that's what's kind of new. It's just a game changer. It is just amazing to look at some of the statistics. And then the other thing I would wanna say is that nobody's safe anymore. Right? Nobody is safe. Everybody is getting people coming at them to try to get their valuable data. So and the mainframe is no different. Right? The hacker and the mandates don't care where your data is. They're after your data, and they're gonna get it whatever platform it sits on. So, so that's really why we're here to talk to you. It's just this new state of security and compliance, if you will, or maybe not new but escalated. So so let's talk a little bit about the product that we're introducing to market. And to do that, I'm gonna turn it over to Chris Law, and then I'll come back to you to kinda talk about where it fits into your organization. Sounds good. Way there, Chris. Thanks, Barbara. So yeah. So we, have been sending out communications on this new security first terminal emulation solution called Secure Host Access, and Secure Host Access has basically, has three tiers. So the first tier is pro, and that's really the desktop terminal emulation. A lot of folks are familiar with that. That's what installs on Windows, connects to a mainframe, host systems. It's got, basic security features, you know, TLS 1.3, some data redaction of host on host screens. So redacting data that, might be sensitive on host screens, that type of, feature is available in at the pro tier. And then the, if you go to the right a bit, the enterprise tier adds management to the desktop terminal emulation. So once you have sort of the central management capability, in place, then you can add integration with your identity and access management solution, and that enables things like multi factor authentication, single sign on, and then the ability to, centrally manage your, host access to state. You know, your end users, your sessions, your everything that, is related to your host systems and configurations can be centrally managed. And then, going further to the right, and into the Anywhere realm here, that's the Anywhere tier, we add onto all of everything I just talked about. So this is in addition to everything I talked about. You add the thin client, the web client, And that also enables, things like multi factor authentication for web based users and single sign on and so forth. The other things I talked about for kinda thick and thin clients, but also allows an administrator to centrally manage that entire, terminal emulation estate from a single location. So they can configure sessions and other custom configurations for end users. End users don't have to be involved in that sort of technical process, if you will, making it much easier for, you know, organizations to keep their end users, efficient and productive and and focus that work on on the administrator. So a very powerful powerful solution really focused on security first and, you know, available today, Secure Host Access. With that, let's continue with, some of the things that are, you know, driving why we're doing this Secure Host Access solution, Barbara. Yep. So it really comes from two different places. It comes and and this is at a security level. Right? So, so the left hand column speaks to our ability with Securals access to help you add at least, if not more, two layers of defense in-depth between that end user that's trying to get access to your system and the system itself. And what do I mean by that? So, with OnWeb today, you may well route your end users through your IAM, and that is what is in Secure Host Access. Now with Secure Host Access, as Chris kinda talked about, we have the ability to route all of the traffic going to the mainframe, all of the terminal emulation traffic, both thick and thin through that IAM. We're one of the only ones that can do this with thick. In fact, we are the only one, sorry, that can do this with your thick client access. Now we're gonna get into, you know, what OnWeb is and and compared to Secure Us Access. So I'll get into that in just a little bit. But, really, what we're talking about here is that ability to have an emulator that, is for each one of your unique use cases in your organization as well as being able to add these layers of defense in-depth. And the other thing I would say is that this is because this is a, product that is based on specifications, we're actually, in the place where we can change with you. Right? So you may have a need. Let's just talk outside of terminal emulation for a minute, in your organization to change your IAM. Right? You may need to go from an LDAP repository where you're just simply using usernames and passwords to more of a two factor or multi factor via OIDC or SAML. Think of your, IAM vendors, Ping. There's just so many out there. Okta that are now really offering the enterprise two or more factors for authentication. This is why we're in this game. We're we're going to enable you to leverage that same investment that you're making in the enterprise to restrict and control access to the mainframe, or any other host based platform that you're using terminal information for today. So so this is that is the left hand column. Right? Is we're going to help you route all of your terminal traffic through your IAM. Now on the right hand, column, which is also where a lot of change is happening, and that's in this mandate world. You may not realize, most of you should, just the plethora of security mandates that are either coming down or updating to require stronger authentication. Now we're gonna talk to you a lot today about authentication and authorization. Right? But they're also mandating other things. So let's make sure we're understanding that. Right? They mandate they can mandate encryption, redaction. There's all sorts of security things that you will need to do to protect your personally identifiable or credit card information, and we do all of that, by the way. But today, we're really talking about adding or leveraging that IAM. But in these new mandates or updated mandates, they are now calling for two or more factors of authentication in order to do business with whomever has the regulation in place. So let's tear that apart a little bit. Dura is something that faces the EU. Right? Not only the EU, but predominantly in the EU, and it is now requiring multifactor authentication. That's a relatively new regulation we have had, for example, GDPR out there. GPR required strong authentication, right, but did not necessarily call out multifactor. There's a fairly new regulation. When I say new, I'm talking about in the last twelve, eighteen months. That's the state of New York. Right? In order to do business with the state of New York financial services, you now have to have multifactor authentication. In The US federal mandates have been updating, updating their regulatory compliance for years. Right? Started way back in 2013 when we got the it was one of the first breaches. It was the OPM breach, office of personal management. It was a user ID and password that was used to get in the system. Federal government came out and said, whoop. No more usernames and passwords. Can't do that anymore. And they have continually updated and updated and updated. And now today, it's it's not no usernames and passwords. It is multifactor authentication in order to do business with the US federal government. So, another one I wanted to mention is PCI DSS. Right? So PCI DSS, up until March 31, always thought multi always dealt with multifactor as a best practice. They did mandate it a a year or so ago in certain situations. Games change. Today, it's multifactor all the way. No longer best practice. It's no longer in certain situations. It's all the time in order to protect credit card information. I could go on and on for hours. Just the amount of regulatory compliance that is either new or updated is amazing. Some examples, there's at least four or five more states that have mandates. Almost every country has mandates. And then and then, we think some things are going to change later this year. There's a very good likeliness that HIPAA will require multifactor. So, so it is it's just changing on a regular basis. And by allowing or requiring that emulator to go through your IAM, you will then be able to comply with some of those multi factor requirements, and that's why we're talking about this from two sides. So it's coming at you from a it's the right thing to do. It's certainly more secure, but you also have to do it because of the mandate. And the other thing I will say in all of this is those mandates, I hear a lot of people say, well, they don't call out the mainframe. They don't care where your data is. What they care about is if there is sensitive data to be protected, which typically means, personally identifiable information or credit card information. Now let's be honest. You, as an organization, also wanna protect your IP. So there may not be a regulation out there that required you to protect your IP, but that's just the right thing to do because that is your IP, and you wouldn't want anybody else getting a hold of it. So with all of that said, they don't call out where the data is. You don't see them saying, well, if your data is sitting on an Oracle database. They say if you have that data, you need to require multifactor authentication in order to get to it, Or you need to you need to have multifactor authentication in order to get to my, platform, like the state of New York, state of California, state of Texas. So, so, anyway, that's kind of where we're going, and that's why we've introduced this product. This product, by the way, is not new. It feels new. It has a new name. It's now branded Rocket. So, so you may not have been aware as an OnWeb customer that we had this product before, but we did. It is based off of technology that we did back in the Micro Focus days, continued in the OpenText days. And I it personally, I believe that that is part of why Rocket went after this portfolio of products because they saw this tsunami of change coming in the security and regulatory world and wanted to enable customers to be able to, adapt and change and update their systems in order to respond to those changes. So, so it is not new. I would say the development in this started around 2013, 2015. In that time frame, we delivered a product to market, but it has now been rebranded. So I don't want you to think it while it feels new, it's it's actually been based on years and years of development efforts in conjunction with a lot of customers, to deliver this to market. So sorry to go on. Okay. So let's now let's look at what the product would look like in your organization. Again, after I get done talking about Securals access, I'm gonna actually talk about what OnWeb looks like compared to Securals access. So it looks a little bit familiar to you, but there definitely are differences. So let me talk a little bit about that. So on the left hand column, you will see a terminal emulator. Right? So, what we're talking about here is a thick client, or a thin client. Now you could talk about our web app. I'm sorry. On web as a thin client, but it's a little bit badder than thin. What do I mean by that? It is based on applet technology. This is not based on applet technology. I'll tell you the benefits of that in a minute, but this is straight HTML. So this is a you can use any browser, and it is not actually, host based traffic that you're, getting at the client. You're getting HTML traffic at the client. It is the the, the host based traffic is on the server itself and that server's communication with the host. So so this is the thin client here. The web based client here is total HTML. We call that a zero footprint. And then in addition to that, you also get the thick client. So in my experience working with most customers, they have use cases for both. They have integration that happens at the desktop. And by the way, you likely have that as well because your integration is likely done with that applet. But in Secure Host Access, we we would do that integration mostly through the thick client, but we can also do some integration by adding a, what we call, a connector, to that zero footprint client. So so, anyway, you have lots of options there on that left hand column as to what your terminal emulator will be. The server in the middle, is where the value is. So, and you might think, well, I already have that value, and it that's fair. Right? So you have a server today that services up your applet technology, and you likely have that, integrated with your IAM. I think you'll find in Securus Access that we do a lot more IAMs, and we do a a lot more value here than you would have had. I'm gonna try to pinpoint that. But from an arch architectural perspective, you already have a server. Here's where the secret sauce comes in. So today, when you launch a terminal emulator, even your applet technology, you're still landing at a mainframe login screen, and that's where we can help you. So the first thing we can do is make that server authentication between your terminal emulator and the server. We can make that single sign on if that's what you support in your IAM, and I think you probably do. Most customers do. And what I mean by that is think SAML or OIDC, right, where you log in in the beginning of the day and then and and thirty minutes later, I need to go to another, app in my enterprise, and I'm not prompted for authentication because I'm carrying around a single sign on token. It lasts for so long, and then it'll prompt me again. And and this is all done via security measures. Right? So the more rights you have in the organization, the the, less time that single sign on token should, last because we wanna make sure you are who you say you are to access any sensitive data in the organization. But we because we integrate directly with your IAM, we'll be able to use that single sign on token as well. Now secret sauce. We also can offer that same single sign on experience for the end user to your host. And what do I mean by that? So we can have a secure relationship between our server and a component on the host. I'm gonna talk about mainframes here because it's just I need to pick one, and it's the easiest for me to talk about. So for example, we can, we integrate directly with zMFA sold by IBM. And what that allows, an end user or organization to do is have a single sign on experience. So if you do z m f a today, it does integrate with your IAM, but it also presents to you a workflow that that, that you might want to make more seamless. The standard workflow is it you go to a web page and you copy a token from that web page into your mainframe login screen. What I have found in my experience is a lot of use a lot of organizations want that more seamless. They don't wanna introduce a human into that. And so we have developed direct integration with the MFA. And so what happens behind the scenes is there is no human intervention. Instead, the servers, have a trusted relationship. We map the enterprise user ID to the mainframe user ID. And based on that mapping and our secure relationship, we're able to obtain a one time time limited token. So just let me repeat that. One time time limited Short duration because it's important that this person not, you know, have this token for for a long time. But what's really important here is it's only used for a one time use. So this makes it a lot harder to hack into, a lot harder to breach this security measure, if you will, this defense in-depth. So we map the user ID. We get this one time token. We pass that to the user in an automated fashion, and that user, instead of authenticating at the host, instead of typing in anything or copying anything, they are automatically logged in for a one time use. That is really, again, our secret sauce. So if you paint this whole picture, I got a user logging in in the enterprise. They launch their emulator. We can use single sign on on the front end for your IAM, and then we can use single sign on on the back end. And what happens here is those are two separate login processes that are managed by the server. And because of that, you have now really increased the security here for that end user logging into the mainframe. If we go back to the statistics I showed you about a user ID and a password being, compromised, think about how that would affect you in this environment. Right? That username and a password, obviously, doesn't get you anywhere anymore because now we're requiring two factors. So it's gotta be more than that. And we're having the so the security here is a lot better, but the user interface is also a lot better. That workflow for the user, not having to remember their separate password to log in to the mainframe, and all happening and more secure. So that's really why we're bringing this product to market. Lots more I could talk about here, but that's really the nuts and bolts of why this product is being brought to the market and why we're suggesting that you upgrade. Speaking of upgrade, I think that's the next topic. Yes. So, so so we are suggesting that you upgrade. So this is kind of the architecture of what you have in OnWeb today and what you would get with secure host access. So today, OnWeb is this applet technology, and the applet could either be Java or ActiveX. And that's old school. Sorry. It is. It's just and it's old school from a security perspective, and it's also an old school from today's technology. Most of the browsers out there have deprecated this technology. We have launchers now to help you still use the technology, but not in a deprecated way. But what happens here is it requires something installed at the desktop. Well, that is not why you bought a web based emulator. So, so there's really a lot of advantages for you moving to Securost access. But you just need to understand that there is a different architecture here. And I'm gonna kinda dig in to what does that mean from you from a pain point perspective, but also what you get from a benefit perspective. So, so understand it is definitely a different technology, different architecture. So let's go ahead and go to the next slide. So, so because that architecture is different, you're gonna find some things that you can't do in the same fashion, and I think that's really important that you understand that. Obviously, you're gonna do a POC. You're gonna walk through this. I actually was delighted. I had a meeting just last week, with an OnWeb customer, and he and that our web sorry. OnWeb customer was really complaining about the update process for that component that sits at the desktop. And we actually talked to them about Securus access and how that component would go away. But because that component is going away, the Securus access web client has to play by the security sandbox issues. And so what do I mean by that? I mean, there is security around your browser that is intentionally put in place to protect you. And so you cannot run things the same way when you don't have a component like the applet that you're talking through. So a couple of examples for me are printing and file transfer. So from a printing perspective, the browser cannot directly print to a printer attached to your device or across the network. Right? Because there are restrictions from browser security. So what you do instead is you print and it goes to a PDF, and that PDF is downloaded. So it's not that you can't print. It's that the printing interface is different. File transfer is another, thing that changes when you're in browser security. Right? To protect you and your end users, we don't want you drilling down on the desktop. When I say we, I just mean from a browser perspective. The browser in itself cannot interrogate the desktop because we don't want them running software on that device because that could introduce malware. That's how thing bad things happen, so we protect you from that. So you you could still do file transfer. It's just done differently. Right? You have to know the file that you wanna transfer, and you can't just go interrogate the desktop. So, so just a little bit of differences there so that you understand that. You'll be able to see that once you put the product in play. And this is done, by the way, in any, any emulator that is not based on Java and ActiveX. So all the emulators out there today, this is not something that is just Securals access. This is all the emulators that have gone to this HTML interface, which is way more secure. So the other thing I want you to know is that migrating to the Secure Host access web will require some manual tasks. We wanna work with you. It's important. You'll see in this whole layout that we wanna partner with you. There is value in you moving to Secure Host Access. There's value for you, and there's value for us. So, but some things are manual. Some things will be minor adjustments. Some things today are not supported. So, you know, we get that. We wanna partner with you. We wanna have that conversation. We can do that one on one. Chris and I do that all the time. If you find something in there that you absolutely have to have and it stops you from moving to Securus Access, we wanna know about it. One of the things that just doing product to product comparison that I wanted you to know right off the bat is today, the web client for Securus Access does not support an HP 3,000 connection. So we we, we do support that in the tech client, so maybe that's the way to do this. But, again, if that's something that you need, I just wanna have a conversation. So this is full transparency where we get that this is just not a move from this product to that product. We get that it's, you know, a pathway. It's a migration, but there's real value. So let's talk a little bit about the value. So, so this product has a different deployment model, and we think it's a great deployment model. Some choices there. Right? So we're trying to go into where, most software vendors try to deploy their products. So we have three choices. The first is a virtual software appliance where you can just take our OVF file and deploy it in any virtual software, technology. Right? VMwares is the one I think about all the time, but there's lots of technologies out there that you could just drop our product into. We call this the easy button. Inside, this is a virtual software. No hardware required. Inside of that software appliance, we have an OS, and we maintain that OS for you. What do I mean by that? We have an interface into this software appliance that allows you to update the OS, and it allows you to update the product. But there are some customers that say, nope. I don't want you doing the OS. I wanna do the OS. So if that's true, then we have a Linux OS installer. We ins we support most of the current OSes out there as far as Linux goes. We do expect you to keep current on your OS. We cannot support something that is on its way to end of life or end of support because that's just not in your best interest or ours. So that is available for you. By the way, all of this is in the documentation so you can go read for yourself. I'm just trying to give you the highlights. And then new to this, deployment model is a helm chart install. So inside of our product, inside that black box, we are a containerized product done through orchestration. Think Kubernetes. Lot of customers just like wanting to run on their OS. They also wanna be able to deploy in their own orchestration tool. So we're just now delivering that to market. We did that in June. It's a helm chart install to where you could take our product and deploy it in the platform of your choice and your own orchestration tool. Fairly new, so we wanna make sure that, you know, you take a look at all of that. We have worked with a couple of our customers to partner with them to ensure that we have minimum viable solution here, but we're open to feedback. So, so what are the real benefits here? There's absolutely no dependency on the client side for Java or ActiveX. I think that's one of the big differentiators between this product and your in your on web product. The other thing is that any modern browser can support this product. Again, no no dependencies. Right? Whether it's Java or anything else. Now we have connectors that we can add in case you need to. If you only want the web based emulator and you need to do some integration, there are some connectors that can help address that, but they are not required. That is use case by use case. Here's something that I think is really valuable from a security security perspective, and that is that all of your host traffic, so think thirty two seventy data stream, stays at the server level. So what that means is the closer you set that server to your host, the the shorter the ability to tap in and get to your thirty two seventy traffic. The traffic from our server to your client is all HTML based. It is not thirty two seventy based. So that is really a security benefit to you taking on this application. A couple other things that I want you to know is that we do quarterly releases. We are DevOps, agile type of a development team. It does not mean that you have to take those quarterly releases, but I think it's important because in this new world that we're living in, with these security vulnerabilities popping, rather it's in scanners or or something like a Log four j, you can depend on us to have a new release out the next quarter, if not sooner to be able to adapt to those vulnerabilities. So you always have a quarter release that you can uptick to either that's for features, but it also could just be to make sure that you are keeping in line with security mandates out there. And then finally, as an OnWeb customer, I think you've kind of been in the place where you're getting annual releases, and we've we've kind of slowed down that train to where it's really about service packs. I think you'll find a very innovative go forward road map with secure host access. We Chris and I can hardly keep track of all of the new things that we're doing, and and it's great. And the majority of that is done based on security. So, so it really is cool going forward to to see you look at our innovative road map. And by the way, and I think we're gonna say it later too, we always want your feedback. Right? So if there's not something on the road map that you want, have a conversation with me. If there are things on the road map that you don't understand, have a conversation with me. This is is we're gonna be transparent with you going forward, and and we want you to engage, and we're gonna give you ways to do that. I think yeah. So this is our advice to you. Right? And it's and and the reason why I'm saying this is because my job is security. Right? So there is so much in this product that will make your terminal emulation landscape more secure. We're suggesting that you look at this sooner than later. And the other reason why I say this is there is no migration that is easy for you. There is no upgrade that is seamless or, totally, you know, an easy thing, or you could just shut the lights off on one and turn the lights off on another. We get that. So but that's why we're asking you to take a look at this sooner than later. The product is available today for you to take for an evaluation, trial, POC, whatever you call those things. In order to get that, you need to reach out to your account representative. I get with all the transition. You may not even know who that is. The email address at the bottom of the screen is we're gonna give that to you again later, but that is the way to get a hold of Chris and I. Chris and I are behind that email address, and we're going to respond to you. And we can that could be as simple as bringing in your account executive. So don't hesitate. If you don't know who that is, we'll get a hold of them. But in my opinion, you really need to start making a plan to upgrade sooner than later. There's a lot in here that is value to you, not only just from an organizational standpoint to get rid of those desktop dependencies, but also from a security perspective. And then, again, we wanna know how we can assist. We may not be able to do everything for you, but we wanna partner with you. And if nothing else, even if it's negative, we wanna hear your feedback. That's what we do for a living. That's, you know, we incorporate all the feedback that we get, into our future. Even if it is negative feedback, we wanna hear from you. So, so I can't remember what the next topic is, but, okay. So now we're gonna talk about product you, Barbara. Yeah. Okay. It's still me. So yeah. So and the reason why Chris and I say this, we're talking to every customer out there from every product, and we have I don't remember what the latest count is. I think we have 17 terminal emulators, so that's kinda why Chris and I tag team with this. And OnWeb customers are mine, so I own the OnWeb, product now as a product manager. So that's why some of these slides are mine and not Chris'. But here we go. So you got to this webinar most likely because you received an announcement on or around July telling you that your product was going into a maturity phase. I hope that didn't cause anxiety, because that certainly wasn't the intention. It's really about the path forward. But let me tell you a little bit about maturity. So first of all, I think you will have seen up to this point that we want you to move to Securus Access. We think it's in your best interest. It's certainly in our best interest because then we're able to focus all of our innovative development on that product. We're not going to innovate on on web anymore. We will continue to support you, so please don't feel like maturity means end of life. It does not. I think that is something that you going back to the, values, Rocket Software does not end of life products. And that's something really important because I'm not convinced you heard that from your predecessor companies. But I will tell you that from a Rocket Software perspective, we do not end of life products. So what does maturity mean? It means we will continue to support you from an on web web to host perspective. You will continue to receive bug fixes and security patches when it needs to happen. What do I mean by when it needs to happen? We will we will first of all, we will, have a road map for you that we will deliver an annual release to you in a service pack update kind of form. You got one of those not all that long ago. So, and I can't remember exactly when I wanna say June. But anyway, a year from then, we will deliver another one to you. Now but the other thing, and this is where the anxiety comes in, is if we have some devastating vulnerability that gets brought to light tomorrow, think Log four j, or something like that, we have your back. We will do a fix for you. We're not walking away from this product. So we will continue to support you from a bug and security update perspective, and you'll get annual releases based on that. And we've got your back if there's something devastating that happens either in your environment or in the market. We will address that. But all the innovation, including new features so what do I mean by that? Let's think about TLS one dot four. That could come out tomorrow. We don't know when it's gonna come out, but we know it's gonna come out because it certainly didn't take long between one dot two and one dot three. When it comes out, that will be done against Securus access, not against on web web host. So that's a way of thinking about that. So, again, in two short phrases, we got your back, but we want you to upgrade. So, Chris, let's talk a little bit more about, the the the product life cycle. Sure. Yeah. Easy to say. Come on. PLC. Thanks, Barbara. Yeah. So you had quite a stretch there. So let me take over, give you a breather for just a sec here. So, yeah, if you think about all the different terminal emulators that kind of have been in our history, and we showed you that on our history slide earlier, there's a lot of legacy companies involved with different product life cycle backgrounds and and policies. And so we took a good, you know, eight months to a year here to really put together our go forward, product life cycle policies for the Secure Host Access product, for Secure Host Access. So, again, it took a long time. I put an exclamation point after published here because, it was such a big effort that involved so many stakeholders, but we're happy to say that that life cycle has been published. It is available for public viewing. You can see it now on the Rocket website. The policies are are new and improved. They're easy to understand. We've been communicating with customers, fairly frequently via various, methods, emails, so forth. But mainly, we want you to know now that you can go to the forum or the docs portal, docs.rocketsoftware.com, and you can access the, new Rocket connectivity product life cycle for secure host access. You know, previously, like I said, you know, there's a lot of different, heritage legacy companies, policies that we were dealing with and bringing forward in all this, and now we're making those policies consistent across all terminal emulators. So we've got a bunch of products now that are in the mature what we call the mature phase, and there's definitions on that on the, public, PLC life cycle page. And then, we've got this secure host access product lifecycle going forward. And the way just to give you a quick overview of what that looks like, you can go check this out online right now if you want, but at a very high level, you get, three years in this general availability slash standard support phase. So you release we release a new version, get three years of, all, you know, full support including bug fixes and innovation. Then in years four and five, the product goes into limited support. You're still getting, you know, pretty much full support, if you will, minus a few things. All the web based documentation is there. You still call tech support. You still get bug fixes and so forth. But may you know, innovations in the in the major release, whatever the latest one is. And then year six and seven, you're in the restricted support phase, and we start scaling back, support policies, and and services a bit. But all in all, a pretty good long, time and basically runway, if you will, for the product version that you're using, of secure host access being supported. So wanted to highlight some of that. That information is all now available on the Rocket Software website. If you have any questions, you can hit us at the, email alias, which we're gonna share, again in just a minute here. So let's talk a bit more about, how we're gonna help you, our commitment to you. We're almost at the end here, so just a few more things. So like Barbara said, on web web to host continues to be supported, you know, critical bug fixes, so forth. We're gonna do our best to, get things to you quickly, address things that come up quickly. You can move at your own pace to Secure Host Access. Well, I think there's some compelling reasons. Barbara, illustrated these nicely earlier. There are many compelling reasons to move to Secure Host Access. There's gonna be a regulatory mandate in your future that says you need multifactor authentication or data redaction or, data encryption, TLS, SSH, and, it's just gonna, you know, force you to have to move in that direction. So that that is something that's happening more and more and that's a lot of what our conversations with customers are about these days. And we're gonna support you through our, you know, your it's really our modernization journey together. So as you go down your path and you need help and, you know, you need help with securing your your host access, we're gonna be here for you. So just keep that in mind, and I'm gonna let Barbara, because she's already had too much rest here, get her back discussing the last couple of points. Thanks, Barbara. Yep. So as we talked earlier, SecureOS Access has a really innovative road map. If you'd like to understand that a little bit better, you're welcome to contact us at that email address. I certainly would go over that with you. Also, if you have, you know, concerns that if there's not something supported in Securys Access that you need supported, again, feel free. I mean, it's a interactive conversation, and we're we're here to help you. And then, as Chris showed you, the product life cycle policies, they're really better than ever. Right? This has got a really good, product life cycle going forward. As Chris and I worked on the product life cycle, you know, we knew that there was gonna be still work to do. And in fact, as an OnWeb web host customer, I can actually tell you I have to already make a change because I did not when so Chris and I actually, again, are the ones that put that product life cycle together and made it public. And the table that you see, I did not add service pack two on there. And so I'm gonna add that, so there will be a change coming there. So if you don't see that, don't let it concern you. It didn't change the product life cycle, but you will notice that it's not on there. So I I will get that added. So, and then finally, right, we just, you know, we just need to hear from you. We wanna know what you like and what you don't like. We get that this is not easy. We get that we're asking a lot of you. But I think you also will receive a lot by making this change. So, but we also understand that no transition is easy. And if there's something that we can do, we would like to know about it. So that's what the email address is up there for, so don't hesitate to reach out. If for some reason we don't get back to you in a timely manner, I have one in the queue now, ping us again. It's okay. It's just Chris and I, and we will get back to you. We just sometimes we get a little busy, but we will get back to you. I promise. So don't you're not you're not going to upset us by saying, hey. I emailed you a couple of days ago and you haven't responded. So, so keep in touch. We wanna know how it's going. And with that, I think, Evan, we're gonna open up the for questions and answers. That's right. Questions anyway. No. That's right. Thank you very much, Barbara and Chris. I I don't see any questions at the moment, but, I know that there's some that come up a lot. I don't know if there's anything that you either if you want to, bring up now while we give everyone a minute to to think about it. Otherwise, I think we can wrap things up. So so sure, Evan. Thanks. Yeah. One one thing that does come up quite a bit is, especially for web to host and, Barbara, you and I worked on reflection for the web for a long time, really Java based solution. You had to get an applet out to the end user desktops, and you you covered this earlier. But just to reiterate that point, the Secure Host access solution, the web portion, what is the Java requirement on the end user desktop, if any? Yeah. So on a desktop, there is none whatsoever. It is still a Java based product that is but Java is on the server, of course. Yep. And and kind of the interesting thing, it's not just that the Java isn't required on the desktop, but it's a game changer because, you know, the browsers deprecated all of that technology before, and you had to use different modes. Right? I think compatibility mode, and there was just some other things. We did a lot in the on web web to host product to help customers so that they could continue to use that Java applet in their environment. But it's but then it wasn't just downloading the, applet. It was installing it on the desktop. So, so all of that goes away with the secure host access web client. There is no desktop dependencies that kind of freeze you to use any, emulator sorry, a a browser that's out there. You know, you do you do have to be aware of of the browser restrictions. Right? But those are all in there for the right reasons. They are there to protect you, not to just irritate you. But it is a different way to do business. But yeah. No. No more. I would say no more job or active x dependencies on the desktop, Chris, but even more than that. No requirements for something to reside on the desktop. It's a case by case user case. You can install something if you think it will help in a certain use case, but it is never required. Are you then seeing customers use, the web piece of Securost access on other types of devices like tablets and phones and that type? Yep. Yep. In fact, today, we fully support, iOS on almost any device. Phone, tablets are great. We're a little farther away from Android. It's a little bit of a different, thing. But the other interesting thing is we also support the Safari browser. Right? So yeah. So by getting off of that dependency, it opens up a lot of options for you. But we absolutely support mobile devices. And we see a lot of customers using them. Right? When you think about retail or even the travel, where you get things queued up, think about a line where you're in a checkout line or for airline check-in. Right? That's where we see tablets being used, where somebody can have that same emulator on a tablet, and they're walking down the line to help their customers ease the pain of standing in that queue. That's a great example where tablets come into play. And how much do customers find value in being able to manage everything from a central location location, you know, from a dashboard? Yeah. You know, that that is one thing. We didn't spend a lot of time here, but I think it's really, really important. So a lot of on web web to host customers also use a thick client or, you know, today they're managing that, from their administrative console. But when you have this ability to manage both thick and thin from the same place and, honestly, a lot of organizations move to thin for that administrative ability to manage. Right? But with Secure Host access, you have the same ability to manage thick. So what do I mean by that? If you are using a thick client emulator today and you moved to, for example, TLS from SSL I know that it may sound old school to you, but I still got customers that are doing it. And when you do that, you've gotta go change every session, and that could be overwhelming to you. I had one large bank I talked to. It took them for a year to go change every one of their sessions to use TLS and the right algorithms and the right certificates. If you do that through Securus access, it can all be done from a centralized standpoint. No sessions have to be changed at the desktop. Ten years when we started down this road, we only had the ability to overlay a session. So we had to change the session, and then when we push it down to the desktop, we overwrote all the user preferences. But we've got a lot of work since then, and we no longer have to overwrite those user preferences. We can make a surgical change. So just say, for example, TLS one dot o to one dot three or one dot two to one dot three and nothing else. So they still get, you know, their pink background and their and their, different buttons on their toolbar, for example. We don't upset the end user. We make a surgical change. So it's a game changer for people that need to use both thick and thin. They the there's just nobody else does this. Nobody else manages thick like we do. Again, you don't have to do that, but it is just another one of those benefits that comes along with the product. And we, by the way, did that because of requests for customers. All this stuff we have in Securus Access was not done because we thought it was cool. It was done because a customer expressed need to do that. That when large federal government customer came to us ten years ago and said, you know what? I need both thick and thin, but it would be really nice if I could manage thick like I do thin. And that's what we got here today. Yeah. Probably and the central management and everything probably saves a lot of help desk calls from end users, I would suspect. Yeah. Absolutely. And the same with the new single sign on with the passwords. Right? Because because those mainframe administrators are resetting passwords all the time. It's a different password than you've got out in the enterprise. So you don't remember it or worse, you write it down. I mean, there's lots of reasons why that helps you from both a security perspective, but also from an administrative perspective. Password doesn't we don't we don't do anything with the password. We just don't rely on it anymore. Instead, we're relying on that one time token that we get from the component on the mainframe. Yeah. Yep. Great. Thank you. Lots of pretty cool stuff. You bet. Yep. Well, this was great. Alright, Evan. Yep. I think we got added time. Speaking part. Yep. Well, everyone, I I appreciate you all being here today. I think this was a wonderful session. If you do have questions that come up after this, please don't hesitate to reach out. You've got the email address here, rocketconnectivity@RocketSoftware.com. That will get your question to Chris and Barbara, and we can get you an answer. So, thank you again for being here, and, we will be in touch. So thanks again. Thank you. Have a great day. Have a great day. Bye. Bye now.