-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set the name shown to the user (client) to be the server name specified in the install script #491
Comments
Oops |
You guys are fast :-) |
Any way is fine! Thanks for reporting the bug. |
Can you provide a screenshot of what you are referring to? |
Let me know if you need more clarification but i figured that was more useful than screen shots from client devices. |
This makes sense, but we're going to take a look at this after we finish the 1.0 milestone. |
Found this issue while looking to see if I had missed a config step. It was bugging me, so I went ahead and made initial changes to line up with the output I had hoped to see. Mainly a starting point for a second convenience feature I added for myself, but I kept it separate, just in case this is along the lines of what you were looking to do. If it is, let me know and I'd be happy to clean it up, get some additional testing in and PR it back. master...bkono:feature/server-name-in-mobileconfig |
Thanks! We're open to receiving a PR for it. |
…WS EC2 Normalized the various cloud_server_name entries to just algo_server_name. Integrated algo_server_name into the mobileconfig template as well as powershell. If a default name is provided, the original behavior of IP_subject_alt_name will be used to avoid conflicts. Also updated the Name tag in the cloudformation template to utilize the StackName (which is based on the algo_server_name).
Great. PR is pushed #959 with screenshots of expected behavior in the comments. |
…emplates EC2 Name tag in the cfn stack, VPNName in client_windows.ps1 and the mobileconfig files all make use of the algo_server_name with a default of the original Algo VPN naming when the server name is left at default algo or algo.local.
OS / Environment
AWS
Summary of the problem
During install a server name can be specified in the script. (A query could also be made for a "friendly name".
Regardless of what is entered, the name used is "Algo" for:
AWS Console
Apple MobileConfig
(and probably others that I can't test)
Steps to reproduce the behavior
normal install
The way of deployment (cloud or local)
cloud
Expected behavior
use the specified server name or optionally a friendly name/tag
Actual behavior
Full log
The text was updated successfully, but these errors were encountered: