Scripting - How do you store your credentials and call them later?

dafyre

Try this script...

#!/bin/sh

# Setting (office) offname variable
read -p 'What office are you in?: ' offname

# Setting (computer username variable) compuser variable
read -p 'Enter this computers username (SAMAccountName) IE jdoe: ' compuser

# Setting the asset tag (tagnumber) variable
read -p 'Enter this computers asset tag: ' tagnumber

sudo scutil --set HostName $offname$compuser
sudo scutil --set ComputerName $compuser$tagnumber
sudo scutil --set LocalHostName $offname$compuser$tagnumber

Then just run the script with ... sudo ./myscript.sh

You have to enter your password once at the beginning.

dafyre

@DustinB3403 said in Scripting - How do you store your credentials and call them later?:

Woot got it!

Sweet! What did you wind up doing?

DustinB3403

#!/bin/sh

read -s -p "Enter a wheel username: " USER
read -s -p "Enter a password for wheel: " PASS

# Setting (office) offname variable
read -p 'What office are you in?: ' offname

# Setting (computer username variable) compuser variable
read -p 'Enter this computers username (SAMAccountName) IE jdoe: ' compuser

# Setting the asset tag (tagnumber) variable
read -p 'Enter this computers asset tag: ' tagnumber

echo $PASS | sudo -S scutil --set HostName $offname$compuser && sudo -S scutil --set ComputerName $compuser$tagnumber && sudo -S scutil --set LocalHostName $offname$compuser$tagnumber

DustinB3403

@dafyre thanks for helping out there, it was almost there the sudo -S bit was all it needed, but for some odd flipping reason it recommends using -U flag as well which is weird.

But at least it works, now to fold this into the larger script and see how it all works.

dafyre

@DustinB3403 said in Scripting - How do you store your credentials and call them later?:

@dafyre thanks for helping out there, it was almost there the sudo -S bit was all it needed, but for some odd flipping reason it recommends using -U flag as well which is weird.

But at least it works, now to fold this into the larger script and see how it all works.

I'll be over here in the corner with my hard hat on, watching for nuclear fallout, lol.

Glad you got it going!

DustinB3403

@dafyre said in Scripting - How do you store your credentials and call them later?:

atching for nuclear fallout, lol.

I've already made a backup of the master script before edits.

DustinB3403

I think my header really sells it.

DustinB3403

I'm of course just kidding, lord knows I'd actually get dragged to court with a disclaimer like this. . .

Time to find the GNU license and insert that. . .

IRJ

I'm glad you found a solution, but have you considered ansible for tasks like this?

DustinB3403

@IRJ said in Scripting - How do you store your credentials and call them later?:

I'm glad you found a solution, but have you considered ansible for tasks like this?

Have you consider our lord and savor jesus christ?

FFS man...

Of course I have I just don't understand it as all of their documentation is god awful and I'd have to take numerous pounds of coke up the backdoor to understand what the hell I'm supposed to do.

On a positive note, if you want to jump on a skype call some time or another I'd be happy to learn if you're willing to teach.

stacksofplates

@DustinB3403 said in Scripting - How do you store your credentials and call them later?:

@IRJ said in Scripting - How do you store your credentials and call them later?:

I'm glad you found a solution, but have you considered ansible for tasks like this?

Have you consider our lord and savor jesus christ?

FFS man...

Of course I have I just don't understand it as all of their documentation is god awful and I'd have to take numerous pounds of coke up the backdoor to understand what the hell I'm supposed to do.

I don't know what you're on. It's some of the better documentation. I'd be interested to see what specific parts you are referencing.

DustinB3403

@stacksofplates said in Scripting - How do you store your credentials and call them later?:

@DustinB3403 said in Scripting - How do you store your credentials and call them later?:

@IRJ said in Scripting - How do you store your credentials and call them later?:

I'm glad you found a solution, but have you considered ansible for tasks like this?

Have you consider our lord and savor jesus christ?

FFS man...

Of course I have I just don't understand it as all of their documentation is god awful and I'd have to take numerous pounds of coke up the backdoor to understand what the hell I'm supposed to do.

I don't know what you're on. It's some of the better documentation. I'd be interested to see what specific parts you are referencing.

Specifically using it to administrator Apple OSX laptops and workstations is what I'm particularly interested in. We have very few linux systems here that would require automation on any scale.

DustinB3403

Like 85-90% of this office is OSX, so anything to help reduce that overhead would be great. I've even posted here about looking at all of these automation tools and which was best and it turned into a this one is cool, but it doesn't do that one thing you absolutely need.

DustinB3403

PS I learn from seeing and doing, rather than reading. Just as an FYI.

DustinB3403

And the peanut gallery falls silent.

stacksofplates

So I admittedly don't know anything about Macs because I don't care to, but here is a simple way to do this with Ansible.

---
- name: Set crap with scutil
  hosts: macs
  become: true
  user: dustin
  vars:
    -computername: "this_computer_sucks"

  tasks:
    - name: set computername
      shell: "scutil --set ComputerName {{ computername }}"

    - name: set hostname
      shell: "scutil --set HostName {{ computername }}"

    - name: set localhostname
      shell: "scutil --set LocalHostName {{ computername }}"

If spacing is off, I'm on my phone so suck it up.

DustinB3403

@stacksofplates so that seems simple enough, how do you put in the custom details like I am pushing to these 1 by 1?

the office location, the expected user and the asset tag to create a single -computername ?

Also since we're on it, how do you use tools like brew.sh to install and update third party software?

IRJ

@DustinB3403 said in Scripting - How do you store your credentials and call them later?:

@IRJ said in Scripting - How do you store your credentials and call them later?:

I'm glad you found a solution, but have you considered ansible for tasks like this?

Have you consider our lord and savor jesus christ?

FFS man...

Of course I have I just don't understand it as all of their documentation is god awful and I'd have to take numerous pounds of coke up the backdoor to understand what the hell I'm supposed to do.

On a positive note, if you want to jump on a skype call some time or another I'd be happy to learn if you're willing to teach.

Chill out man. The whole point of being in IT community is to learn new things. There's always more than one way to skin a cat, it's not horrible knowing there are other options.

Ansible really isn't that difficult and you'll save a ton of time in the long run.

DustinB3403

@IRJ I'm salty because I've brought automation tools like Anisble, chef, puppet and salt up before and the only responses have been minimal at best.

Can we have an in-depth this is how to get started conversation?

IRJ

@DustinB3403 said in Scripting - How do you store your credentials and call them later?:

@stacksofplates so that seems simple enough, how do you put in the custom details like I am pushing to these 1 by 1?

the office location, the expected user and the asset tag to create a single -computername ?

Also since we're on it, how do you use tools like brew.sh to install and update third party software?

To answer this question, you need to edit ansible hosts file. You would add the IPs to the group. You can be as granular as you want

[macs]
192.0.2.101
192.0.2.102
192.0.2.103

[linux]
192.0.2.201
192.0.2.202

[macbooks]
192.0.2.102
192.0.2.103

Solved Scripting - How do you store your credentials and call them later?