Tech Debug

When you are building Windows Server 2012 R2 base images (vSphere Templates) using packer on vSphere (using vmware-iso packer builder); the process usually relies on the windows server to get an IP address automatically via DHCP. This allows the packer builder to then communicate to the server over WinRM and complete the provisioning. What happens when there is no DHCP available in your vSphere VM Network? The easy solution is to have the bootstrap of the windows server set a static IP for the server.

After being asked to use Visual Studio 2015 for F#{.tweet-hashtag} Development, I decided it’s way more lightweight to to develop it on my Mac using Sublime Text 3. Software you need installed: Install Mono on your Mac Of course Sublime Text 3 And the best package manager for Sublime, Package Control. Install (using package control) these packages with package control in Sublime Text: F# – Gives you syntax Highlighting F-Sharp – Autocomplete, tooltips, definitions, etc.

You’ve downloaded your purchased Windows 10 ISO from Microsoft, and you’ve managed to create a bootable UEFI USB stick. Now you’ve decided to run Windows 10 in VMWare Fusion Pro on your Mac. Yet the USB stick can NOT be booted from. There is a solution. VMWare fusion has some (unsupported) EFI options you can enable to effect a USB boot. First you’ll want to create a Windows 10 VM in VMWare Fusion.

I’ve been trying to find a production platform for Edda, the Netflix OSS app for tracking AWS resources. The application is written in Scala, which gets compiled as Java bytecode. The build toolset used by Netflix is gradle, and they deploy the application for testing into Jetty. Jetty can be used in a production environment, but the setup that comes with the build set with Edda is not really designed with a production server in mind.

Now the madness with ADFS2 SAML assertions via WS-Trust 1.3 – and how they are not valid for use with Amazon Web Services (AWS). lexx:saml$ aws sts assume-role-with-saml --role-arn $role --principal-arn $principal --saml-assertion $assertion<br /> A client error (InvalidIdentityToken) occurred when calling the AssumeRoleWithSAML operation: Responses must contain SubjectConfirmatonData with a Recipient and NotOnOrAfter This failed due to a missing Recipient attribute on the SubjectConfirmationData element. Of course; I can’t modify the assertion to add the missing Recipient; as the SAML token is signed:

According to Wikipedia, Microsoft Active Directory Federation Services (ADFS) is: … a software component developed by Microsoft that can be installed on Windows Server operating systems to provide users with single sign-on access to systems and applications located across organizational boundaries. It uses a claims-based access control authorization model to maintain application security and implement federated identity. ADFS can provide Single sign as an identity provider to users, but what if a developer needs the same sign on outside of “browser land”?