Topic
  • 2 replies
  • Latest Post - ‏2013-03-18T00:14:57Z by ShigeT
ShigeT
ShigeT
11 Posts

Pinned topic Custom URL Scheme (Android)

‏2013-03-13T06:17:26Z |
Hi,

I want to use "Custom URL Scheme".
(https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Custom%20URL%20Scheme)

But it does not work well in Android.

Verification procedure is as follows.

1. install Mobile Client
2. Launch browser app(e.g. opera)
3. Enter the following URL

bigfix://pre-enroll?server=<Server URL>

=> the following error was displayed in the Mobile Client
"Registered URL is invalid"

It works correctly with the same URL in iOS.
I tried it in Android 2.2 and 4.0.
Thanks,
Shige
Updated on 2013-03-18T00:14:57Z at 2013-03-18T00:14:57Z by ShigeT
  • SystemAdmin
    SystemAdmin
    184 Posts

    Re: Custom URL Scheme (Android)

    ‏2013-03-16T00:39:28Z  
    Hi Shige,

    I was able to reproduce this.

    The problem is that this feature was originally intended to allow browsers
    to complete the final steps of the enrollment process. Initiating the
    enrollment process using bigfix:// URLs was not part of the original plan.

    The good news is that everything works fine when I remove the check so we'll
    keep testing it for a couple of days and should everything go ok then we'll
    include this fix in the 2.1 Android agent (to be released around the end of March).

    Cheers
    Miguel
  • ShigeT
    ShigeT
    11 Posts

    Re: Custom URL Scheme (Android)

    ‏2013-03-18T00:14:57Z  
    Hi Shige,

    I was able to reproduce this.

    The problem is that this feature was originally intended to allow browsers
    to complete the final steps of the enrollment process. Initiating the
    enrollment process using bigfix:// URLs was not part of the original plan.

    The good news is that everything works fine when I remove the check so we'll
    keep testing it for a couple of days and should everything go ok then we'll
    include this fix in the 2.1 Android agent (to be released around the end of March).

    Cheers
    Miguel
    Hi Miguel,

    Thanks for your reply.

    > The problem is that this feature was originally intended to allow browsers
    > to complete the final steps of the enrollment process. Initiating the
    > enrollment process using bigfix:// URLs was not part of the original plan.

    I see.

    > The good news is that everything works fine when I remove the check so we'll
    > keep testing it for a couple of days and should everything go ok then we'll
    > include this fix in the 2.1 Android agent (to be released around the end of March).

    OK! Thanks!

    Shige